Linux Kernel 2.6.11.8 init_posix_timers memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel 2.6.11.8 and classified as problematic. This vulnerability affects the function init_posix_timers. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2009-2767. Moreover, an exploit is present.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel 2.6.11.8 (Operating System). This affects the function init_posix_timers. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The init_posix_timers function in kernel/posix-timers.c in the Linux kernel before 2.6.31-rc6 allows local users to cause a denial of service (OOPS) or possibly gain privileges via a CLOCK_MONOTONIC_RAW clock_nanosleep call that triggers a NULL pointer dereference.

The issue has been introduced in 03/02/2005. The weakness was disclosed 08/14/2009 by Tavis Ormandy (Website). The advisory is shared at lkml.org. This vulnerability is uniquely identified as CVE-2009-2767. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details and a public exploit are known.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1626 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 40629 (Fedora 11 : kernel-2.6.29.6-217.2.8.fc11 (2009-8684)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 195000 (Ubuntu Security Notification for Linux, Linux-source-2.6.15 Vulnerabilities (USN-852-1)).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (52317), Exploit-DB (33148), Tenable (40629), SecurityFocus (BID 35647†) and Secunia (SA37105†). The entries VDB-49049, VDB-50151, VDB-50149 and VDB-49717 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.4
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.4
VulDB Temp Score: 7.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 40629
Nessus Name: Fedora 11 : kernel-2.6.29.6-217.2.8.fc11 (2009-8684)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍

OpenVAS ID: 64707
OpenVAS Name: Fedora Core 11 FEDORA-2009-8684 (kernel)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/02/2005 🔍
07/13/2009 +1594 days 🔍
08/06/2009 +24 days 🔍
08/14/2009 +7 days 🔍
08/14/2009 +0 days 🔍
08/14/2009 +0 days 🔍
08/20/2009 +6 days 🔍
08/24/2009 +4 days 🔍
03/18/2015 +2032 days 🔍
02/27/2025 +3634 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: lkml.org
Researcher: Tavis Ormandy
Status: Not defined
Confirmation: 🔍

CVE: CVE-2009-2767 (🔍)
GCVE (CVE): GCVE-0-2009-2767
GCVE (VulDB): GCVE-100-49437

OVAL: 🔍

X-Force: 52317
SecurityFocus: 35647 - Linux Kernel 'PER_CLEAR_ON_SETID' Incomplete Personality List Access Validation Weakness
Secunia: 37105
Vulnerability Center: 23272 - Linux Kernel < 2.6.31-rc6 CLOCK_MONOTONIC_RAW Local Privilege Escalation Vulnerability, Low

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/18/2015 15:15
Updated: 02/27/2025 11:13
Changes: 03/18/2015 15:15 (64), 02/13/2017 10:22 (10), 08/20/2021 08:01 (4), 08/20/2021 08:07 (1), 12/07/2024 16:49 (25), 02/27/2025 11:13 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!