Kernel memory exhaustion via Radeon reset leak
Published Aug 15, 2026 · Updated Aug 15, 2026
Memory leak in the Radeon ring restore path in Linux 3.6 and later allows local users to exhaust kernel memory through repeated GPU resets. When radeon_ring_lock() fails, radeon_ring_restore() returns without freeing the ring backup buffer whose ownership it accepted. Access to a Radeon GPU and repeated reset-time lock failures are required, with each failure consuming additional kernel memory.
Summary
What happened
Memory leak in the Radeon ring restore path in Linux 3.6 and later allows local users to exhaust kernel memory through repeated GPU resets. When radeon_ring_lock() fails, radeon_ring_restore() returns without freeing the ring backup buffer whose ownership it accepted. Access to a Radeon GPU and repeated reset-time lock failures are required, with each failure consuming additional kernel memory.
The record
- CVE
- CVE-2026-74416
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=3.6
- Affected versionversion=55d7c22192becd0ec827a6901899ff56fa985658 <06dc892561f5a08b2493c34c8ec2cb94dea33159
- Affected versionversion=55d7c22192becd0ec827a6901899ff56fa985658 <07c213f3499dd72e2922c1c73fe9ffea24874bef
- Affected versionversion=55d7c22192becd0ec827a6901899ff56fa985658 <1c9ba32308c02c198c378fcdf06be9ffc3111147
- Affected versionversion=55d7c22192becd0ec827a6901899ff56fa985658 <63912418f1fbb6456ea04bbcdf8f4d5090d23350
- Affected versionversion=55d7c22192becd0ec827a6901899ff56fa985658 <82f1d6042611d45b8b9de423bbcb4e0ced9ec62b
- Affected versionversion=55d7c22192becd0ec827a6901899ff56fa985658 <919e3e398bf301c6418dffdcd5e5c4fd9be39cf7
- Affected versionversion=55d7c22192becd0ec827a6901899ff56fa985658 <ccc42187fc2d0720947a63ce1b9e399d2c068ff4
- Affected versionversion=55d7c22192becd0ec827a6901899ff56fa985658 <eecfb76129ebef7e3aa41e18a4668cd91dfc6267
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