CVE-2010-4083: Low severity Linux Linux kernel vulnerability
Description of problem: The semctl syscall has several code paths that lead to the leakage of uninitialized kernel stack memory (namely the IPCINFO, SEMINFO, IPCSTAT, and SEMSTAT commands) during the use of the older, obsolete version of the semidds struct. The copysemidtouser() function declares a semidds struct on the stack and copies it back to the user without initializing or zeroing the 'sembase', 'sempending', 'sempendinglast', and 'undo' pointers, allowing the leakage of 16 bytes of kernel stack memory. The code is still reachable on 32-bit systems - when calling semctl() newer glibc's automatically OR the IPC command with the IPC64 flag, but invoking the syscall directly allows users to use the older versions of the struct.
Reference: http://www.openwall.com/lists/oss-security/2010/10/06/6 http://www.spinics.net/lists/mm-commits/msg80234.html
Acknowledgements:
Red Hat would like to thank Dan Rosenberg for reporting this issue.
Other sources
The copysemidtouser function in ipc/sem.c in the Linux kernel before 2.6.36 does not initialize a certain structure, which allows local users to obtain potentially sensitive information from kernel stack memory via a (1) IPCINFO, (2) SEMINFO, (3) IPCSTAT, or (4) SEMSTAT command in a semctl system call.
— Launchpad
Affected Software
Remediation
Patch Available
Patch Available
Patch Available
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2010-4083?
CVE-2010-4083 is considered to have moderate severity due to its potential for information leakage.
How do I fix CVE-2010-4083?
To mitigate CVE-2010-4083, it is recommended to update to a more recent version of the Linux kernel that does not use the affected semid_ds structure.
Which versions of the Linux kernel are affected by CVE-2010-4083?
CVE-2010-4083 affects the Linux kernel versions prior to 2.6.36 and several specific versions of SUSE and Debian distributions.
What types of data are leaked due to CVE-2010-4083?
CVE-2010-4083 leads to the leakage of uninitialized kernel stack memory which could potentially expose sensitive data.
Is CVE-2010-4083 exploitable remotely?
CVE-2010-4083 is more likely to be exploited locally since it involves kernel memory access through system calls.