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