Local privilege escalation via debugfs heap overflow
Published Oct 21, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in the Linux kernel through 5.14.14 allows local users to escalate privileges through AMDGPU debugfs. parse_write_buffer_into_params passes the user-controlled write length to copy_from_user, which copies into a fixed 40-byte heap buffer without a bound check. Exploitation requires the AMDGPU display driver, debugfs, and write access to the affected entry; successful corruption can crash the system or execute code with kernel privileges.
Summary
What happened
Heap-based buffer overflow in the Linux kernel through 5.14.14 allows local users to escalate privileges through AMDGPU debugfs. parse_write_buffer_into_params passes the user-controlled write length to copy_from_user, which copies into a fixed 40-byte heap buffer without a bound check. Exploitation requires the AMDGPU display driver, debugfs, and write access to the affected entry; successful corruption can crash the system or execute code with kernel privileges.
The record
- CVE
- CVE-2021-42327
- Published
- Oct 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- CVE-2021-42327 GPU kernel driver SLUB overflowfunctional · demonstrated
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