blob: 89c5fdc0589cc8660d09863c1be72c59e43a78e0 (
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
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
Candidate: CVE-2004-0415
References:
CONECTIVA:CLA-2004:879
URL:http://distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000879
GENTOO:GLSA-200408-24
URL:http://www.gentoo.org/security/en/glsa/glsa-200408-24.xml
MANDRAKE:MDKSA-2004:087
URL:http://www.mandrakesecure.net/en/advisories/advisory.php?name=MDKSA-2004:087
REDHAT:RHSA-2004:413
URL:http://www.redhat.com/support/errata/RHSA-2004-413.html
REDHAT:RHSA-2004:418
URL:http://www.redhat.com/support/errata/RHSA-2004-418.html
SGI:20040804-01-U
URL:ftp://patches.sgi.com/support/free/security/advisories/20040804-01-U.asc
XF:linux-pointer-info-disclosure(16877)
URL:http://xforce.iss.net/xforce/xfdb/16877
Description:
Linux kernel does not properly convert 64-bit file offset pointers to 32 bits,
which allows local users to access portions of kernel memory.
Notes:
dannf> Based on the 2.4.27 changelog, I think this is the 2.4 fix:
http://linux.bkbits.net:8080/linux-2.4/cset@411064f7uz3rKDb73dEb4vCqbjEIdw?nav=index.html|src/|src/drivers|src/drivers/char|related/drivers/char/i8k.c
and
http://linux.bkbits.net:8080/linux-2.4/cset@41113629fBqsXgKVAey-EzhZOkS2Lw?nav=index.html|src/|src/net|src/net/atm|related/net/atm/br2684.c
Which doesn't look like it ever made 2.6.
.
dannf> I've asked Al Viro & Marcelo for more info
dannf> Marcelo says:
2.6 avoids the file offset race by having a copy of it at the high
level VFS functions, its safe.
Bugs:
upstream: released (2.4.27-rc5)
linux-2.6: N/A
2.6.8-sarge-security: N/A
2.4.27-sarge-security: N/A
2.4.19-woody-security:
2.4.18-woody-security:
2.4.17-woody-security:
2.4.16-woody-security:
2.4.17-woody-security-hppa:
2.4.17-woody-security-ia64:
2.4.18-woody-security-hppa:
|