|Description||The __secure_computing function in kernel/seccomp.c in the seccomp subsystem in the Linux kernel 220.127.116.11 and earlier on the x86_64 platform, when CONFIG_SECCOMP is enabled, does not properly handle (1) a 32-bit process making a 64-bit syscall or (2) a 64-bit process making a 32-bit syscall, which allows local users to bypass intended access restrictions via crafted syscalls that are misinterpreted as (a) stat or (b) chmod, a related issue to CVE-2009-0342 and CVE-2009-0343.|
|Source||CVE (at NVD; oss-sec, fulldisc, OSVDB, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SuSE, Mageia, web search, more)|
|NVD severity||low (attack range: local)|
|Debian/oldstable||not known to be vulnerable.|
|Debian/stable||not known to be vulnerable.|
|Debian/testing||not known to be vulnerable.|
|Debian/unstable||not known to be vulnerable.|
Vulnerable and fixed packages
The table below lists information on source packages.
|linux-2.6 (PTS)||squeeze, squeeze (security)||2.6.32-48squeeze6||fixed|
The information below is based on the following data on fixed versions.
[etch] - linux-2.6 <not-affected> (Not enabled in 2.6.18)
[etch] - linux-2.6.24 <no-dsa> (unimportant)
CONFIG_SECCOMP has only been enabled in 2.6.26