Kernel panic via per-CPU debug stack reuse
Published Feb 12, 2020 · Updated Aug 6, 2024
Denial of service in the Linux Kernel before 3.3 allows local users to trigger a kernel panic through crafted int3 lock contention. The x86-64 int3 handler enables interrupts while using a per-CPU debug stack, allowing a contended lock to schedule the task out and another task to reuse and corrupt that stack. Local unprivileged execution on an affected real-time kernel is required, and successful exploitation crashes the host.
Summary
What happened
Denial of service in the Linux Kernel before 3.3 allows local users to trigger a kernel panic through crafted int3 lock contention. The x86-64 int3 handler enables interrupts while using a per-CPU debug stack, allowing a contended lock to schedule the task out and another task to reuse and corrupt that stack. Local unprivileged execution on an affected real-time kernel is required, and successful exploitation crashes the host.
The record
- CVE
- CVE-2012-0810
- Published
- Feb 12, 2020
- Updated
- Aug 6, 2024
- Vendor
- Linux Foundation
- Product
- Linux Kernel
- Classifications
- CWE-400, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 3.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo