CVE-2009-2692

Description

From CVE.org

The Linux kernel 2.6.0 through 2.6.30.4, and 2.4.4 through 2.4.37.4, does not initialize all function pointers for socket operations in proto_ops structures, which allows local users to trigger a NULL pointer dereference and gain privileges by using mmap to map page zero, placing arbitrary code on this page, and then invoking an unavailable operation, as demonstrated by the sendpage operation (sock_sendpage function) on a PF_PPPOX socket.

Statement

Red Hat is aware of this issue. Please see https://access.redhat.com/articles/18053.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v2 Score Breakdown

Red HatNVDcve.org
Base Score7.27.2N/A
Attack VectorLocalLocalN/A
Access ComplexityLowLowN/A
AuthenticationNoneNoneN/A
Confidentiality ImpactCompleteCompleteN/A
Integrity ImpactCompleteCompleteN/A
Availability ImpactCompleteCompleteN/A

Vector

Red Hat: AV:L/AC:L/Au:N/C:C/I:C/A:C

NVD: AV:L/AC:L/Au:N/C:C/I:C/A:C

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart

NULL pointer dereferences usually result in the failure of the process unless exception handling (on some platforms) is available and implemented. Even when exception handling is being used, it can still be very difficult to return the software to a safe state of operation.

Integrity,Confidentiality

Technical Impact: Execute Unauthorized Code or Commands; Read Memory; Modify Memory

In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution.

Acknowledgements

Red Hat would like to thank Julien Tinnes (Google Security Team) and Tavis Ormandy for reporting this issue.

Frequently Asked Questions

Want to get errata notifications? Sign up here.