Kernel code execution via cleanup double free
Published May 28, 2021 · Updated Aug 3, 2024
Use-after-free in the Nouveau DRM subsystem in Linux Kernel before 5.9 allows local users with root privileges to execute kernel code. After page-table allocation fails, TTM invokes a destroy callback even though no page table exists, creating the reported double-free cleanup path. Reaching the path requires root and fault injection; hardened slab freelists prevent the reported effect, and upstream maintainers dispute the security analysis.
Summary
What happened
Use-after-free in the Nouveau DRM subsystem in Linux Kernel before 5.9 allows local users with root privileges to execute kernel code. After page-table allocation fails, TTM invokes a destroy callback even though no page table exists, creating the reported double-free cleanup path. Reaching the path requires root and fault injection; hardened slab freelists prevent the reported effect, and upstream maintainers dispute the security analysis.
The record
- CVE
- CVE-2021-20292
- Published
- May 28, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Kernel 5.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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