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