Kernel memory corruption via unchecked ring type
Published Sep 18, 2024 · Updated Aug 5, 2026
An out-of-bounds write in the Linux kernel amdgpu driver allows local users to corrupt kernel memory through DRM ioctls. During ring registration, amdgpu_ring_init indexes gpu_sched with an unchecked ring type, then uses an out-of-bounds num_scheds value to write a scheduler pointer beyond the table. Reachability requires an affected kernel with an AMD GPU using amdgpu; an unprivileged render-node user can cause kernel-memory disclosure, control-flow corruption, or a kernel oops and wedged system.
Summary
What happened
An out-of-bounds write in the Linux kernel amdgpu driver allows local users to corrupt kernel memory through DRM ioctls. During ring registration, amdgpu_ring_init indexes gpu_sched with an unchecked ring type, then uses an out-of-bounds num_scheds value to write a scheduler pointer beyond the table. Reachability requires an affected kernel with an AMD GPU using amdgpu; an unprivileged render-node user can cause kernel-memory disclosure, control-flow corruption, or a kernel oops and wedged system.
The record
- CVE
- CVE-2024-46725
- Published
- Sep 18, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 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 <130bee397b9cd52006145c87a456fd8719390cb5
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <919f9bf9997b8dcdc132485ea96121e7d15555f9
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <a60d1f7ff62e453dde2d3b4907e178954d199844
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <be1684930f5262a622d40ce7a6f1423530d87f89
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <c253b87c7c37ec40a2e0c84e4a6b636ba5cd66b2
- Affected versionversion=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <cf2db220b38301b6486a0f11da24a0f317de558c
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