Local privilege escalation via AMDGPU buffer overflow
Published Nov 19, 2024 · Updated Aug 5, 2026
Heap buffer overflow in Linux kernel AMDGPU debugfs allows local users to escalate privileges through an oversized read request. amdgpu_debugfs_gprwave_read accepts an unchecked size above 4 KiB; wave_read_regs then writes size-divided register words past a fixed 4096-byte heap buffer, and the read path copies the requested length to user space. Exploitation requires access to the amdgpu_gprwave debugfs node on a system using the AMDGPU driver, exposing adjacent kernel memory to disclosure or corruption and allowing a kernel crash or privilege escalation.
Summary
What happened
Heap buffer overflow in Linux kernel AMDGPU debugfs allows local users to escalate privileges through an oversized read request. amdgpu_debugfs_gprwave_read accepts an unchecked size above 4 KiB; wave_read_regs then writes size-divided register words past a fixed 4096-byte heap buffer, and the read path copies the requested length to user space. Exploitation requires access to the amdgpu_gprwave debugfs node on a system using the AMDGPU driver, exposing adjacent kernel memory to disclosure or corruption and allowing a kernel crash or privilege escalation.
The record
- CVE
- CVE-2024-50282
- Published
- Nov 19, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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=4.2
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <2faaee36e6e30f9efc7fa6bcb0bdcbe05c23f51f
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <4d75b9468021c73108b4439794d69e892b1d24e3
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <673bdb4200c092692f83b5f7ba3df57021d52d29
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <8906728f2fbd6504cb488f4afdd66af28f330a7a
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.
Weakness, pattern, technique
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