CVE-2010-4083: Low severity Linux Linux kernel vulnerability

Published Nov 1, 2010
·
Updated

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

11 affected components
debian/linux-2.6
Linux Linux kernel<2.6.36
openSUSE openSUSE=11.3
SUSE Linux Enterprise Desktop=10-sp3
SUSE Linux Enterprise Desktop=11-sp1
SUSE Linux Enterprise Real Time Extension=11-sp1
SUSE Linux Enterprise Server=9
SUSE Linux Enterprise Server=10-sp3
SUSE Linux Enterprise Server=11-sp1
SUSE Linux Enterprise Software Development Kit=10-sp3
Debian Debian Linux=5.0

Event History

Nov 1, 2010
Data Sourced
via Red Hat·09:29 PM
DescriptionSeverityAffected Software
Nov 30, 2010
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Jan 11, 2024
Data Sourced
via Launchpad·09:54 PM
Description
Sep 15, 2024
Data Sourced
via Ubuntu·10:32 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2010-4083?

CVE-2010-4083 is considered to have moderate severity due to its potential for information leakage.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203