Linux Kernel 2.6.36/2.6.36.1/2.6.36.2/2.6.36.3/2.6.36.4 futex_wait memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Linux Kernel 2.6.36/2.6.36.1/2.6.36.2/2.6.36.3/2.6.36.4. Impacted is the function futex_wait. The manipulation leads to memory corruption.
This vulnerability is listed as CVE-2014-0205. There is no available exploit.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in Linux Kernel 2.6.36/2.6.36.1/2.6.36.2/2.6.36.3/2.6.36.4 (Operating System) and classified as critical. This issue affects the function futex_wait. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability.
The issue has been introduced in 10/20/2010. The weakness was presented 09/10/2014 by Mateusz Guzik with Red Hat as futex: Fix errors in nested key ref-counting as confirmed git commit (GIT Repository). It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2014-0205 since 12/03/2013. The exploitation is known to be easy. Attacking locally is a requirement. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The advisory points out:
futex_wait() is leaking key references due to futex_wait_setup() acquiring an additional reference via the queue_lock() routine. The nested key ref-counting has been masking bugs and complicating code analysis. queue_lock() is only called with a previously ref-counted key, so remove the additional ref-counting from the queue_(un)lock() functions. Also futex_wait_requeue_pi() drops one key reference too many in unqueue_me_pi(). Remove the key reference handling from unqueue_me_pi(). This was paired with a queue_lock() in futex_lock_pi(), so the count remains unchanged.
The vulnerability was handled as a non-public zero-day exploit for at least 1421 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 77598 (Scientific Linux Security Update : kernel on SL6.x i386/x86_64), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Scientific Linux Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 122632 (Red Hat Update for Kernel (RHSA-2014:1167)).
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org.
The vulnerability is also documented in the databases at X-Force (95879), Tenable (77598), SecurityFocus (BID 69725†) and Vulnerability Center (SBV-46085†). bugzilla.redhat.com is providing further details. See VDB-13398 and VDB-67524 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 8.4
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 77598
Nessus Name: Scientific Linux Security Update : kernel on SL6.x i386/x86_64
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍
OpenVAS ID: 80056
OpenVAS Name: Oracle Linux Local Check: ELSA-2014-3073
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 7ada876a8703f23befbb20a7465a702ee39b1704
Timeline
10/20/2010 🔍12/03/2013 🔍
09/10/2014 🔍
09/10/2014 🔍
09/10/2014 🔍
09/10/2014 🔍
09/11/2014 🔍
09/11/2014 🔍
09/28/2014 🔍
02/15/2022 🔍
Sources
Vendor: kernel.orgAdvisory: futex: Fix errors in nested key ref-counting
Researcher: Mateusz Guzik
Organization: Red Hat
Status: Confirmed
Confirmation: 🔍
CVE: (vuldb.com) CVE-2014-0205 (🔍)
GCVE (CVE): GCVE-0-2014-0205
GCVE (VulDB): GCVE-100-67523
OVAL: 🔍
X-Force: 95879 - Linux Kernel futex privilege escalation, High Risk
SecurityFocus: 69725 - Linux Kernel CVE-2014-0205 Local Privilege Escalation Vulnerability
Vulnerability Center: 46085 - Linux Kernel Local Privileges Escalation or DoS due to Error in the \x27Futex\x27 Subsystem Reference Counting, Medium
Misc.: 🔍
See also: 🔍
Entry
Created: 09/11/2014 16:26Updated: 02/15/2022 22:06
Changes: 09/11/2014 16:26 (81), 06/06/2017 08:23 (5), 02/15/2022 21:54 (4), 02/15/2022 22:06 (1)
Complete: 🔍
Cache ID: 216:B0E:103
No comments yet. Languages: en.
Please log in to comment.