| 1 |
Candidate: CVE-2006-5753
|
| 2 |
References:
|
| 3 |
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=be6aab0e9fa6d3c6d75aa1e38ac972d8b4ee82b8
|
| 4 |
Description:
|
| 5 |
The listxattr syscall can corrupt user space under certain
|
| 6 |
circumstances. The problem seems to be related to signed/unsigned
|
| 7 |
conversion during size promotion. The function return_EIO returns an
|
| 8 |
int but its used as a ssize_t with a comparison to 0. This causes the
|
| 9 |
range check to fail and copy_to_user copies way too much.
|
| 10 |
The command line "fsfuzz iso9660" can easily reproduce this behavior.
|
| 11 |
Ubuntu-Description:
|
| 12 |
Various syscalls (like listxattr()) misinterpreted the return value
|
| 13 |
of return_EIO() when encountering bad inodes. By issuing particular
|
| 14 |
system calls on a malformed file system, a local attacker could
|
| 15 |
exploit this to crash the kernel.
|
| 16 |
Notes:
|
| 17 |
Bugs:
|
| 18 |
upstream: released (2.6.20-rc5)
|
| 19 |
linux-2.6: released (2.6.20-1)
|
| 20 |
2.6.18-etch-security: released (2.6.18.dfsg.1-13) [bugfix/listxattr-mem-corruption.patch]
|
| 21 |
2.6.8-sarge-security: released (2.6.8-16sarge7) [listxattr-mem-corruption.dpatch]
|
| 22 |
2.4.27-sarge-security: released (2.4.27-10sarge6) [261_listxattr-mem-corruption.diff]
|
| 23 |
2.6.12-breezy-security: released (2.6.12-10.43)
|
| 24 |
2.6.15-dapper-security: released (2.6.15-28.51)
|
| 25 |
2.6.17-edgy-security: released (2.6.17.1-11.35)
|
Parent Directory
| 
Revision Log