blob: f42298e4ed513be506050928af37af07cb50d098 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
Candidate: CVE-2004-0177
References:
Description:
Notes:
jmm> This is resolved by the following patch by tytso:
jmm>--- kernel-source-2.4.18-2.4.18.orig/fs/jbd/journal.c
jmm>+++ kernel-source-2.4.18-2.4.18/fs/jbd/journal.c
jmm>@@ -671,6 +671,7 @@
jmm>
jmm> bh = getblk(journal->j_dev, blocknr, journal->j_blocksize);
jmm> lock_buffer(bh);
jmm>+ memset(bh->b_data, 0, journal->j_blocksize);
jmm> BUFFER_TRACE(bh, "return this buffer");
jmm> return journal_add_journal_head(bh);
jmm> }
jmm> This fix is present in 2.4.27 and 2.6.8, so marking them and l-2.6 N/A
Bugs:
upstream: released (2.4.26-pre4)
linux-2.6: N/A
2.6.8-sarge-security: N/A
2.4.27-sarge-security: N/A
2.4.19-woody-security: released (2.4.19-4.woody2)
2.4.18-woody-security: released (2.4.18-14.3)
2.4.17-woody-security: released (2.4.17-1woody3)
2.4.16-woody-security: released (2.4.16-1woody2)
2.4.17-woody-security-hppa: released (32.4, 62.3)
2.4.17-woody-security-ia64: released (011226.17)
2.4.18-woody-security-hppa: released (62.3)
|
