CVE-2026-74416
drm/radeon: fix memory leak in radeon_ring_restore() on lock failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix memory leak in radeon_ring_restore() on lock failure radeon_ring_restore() takes ownership of the data buffer allocated by radeon_ring_backup(). The caller (radeon_gpu_reset()) only frees it in the non-restore branch; in the restore branch it relies on radeon_ring_restore() to free it. If radeon_ring_lock() fails, the function returned early without calling kvfree(data), leaking the ring backup buffer on every GPU reset that fails at the lock stage. During repeated GPU resets this causes cumulative kernel memory exhaustion. Free data before returning the error.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.6
References 8
git.kernel.org
- stable/c/63912418f1fbb6456ea04bbcdf8f4d5090d23350
- stable/c/919e3e398bf301c6418dffdcd5e5c4fd9be39cf7
- stable/c/07c213f3499dd72e2922c1c73fe9ffea24874bef
- stable/c/1c9ba32308c02c198c378fcdf06be9ffc3111147
- stable/c/eecfb76129ebef7e3aa41e18a4668cd91dfc6267
- stable/c/06dc892561f5a08b2493c34c8ec2cb94dea33159
- stable/c/ccc42187fc2d0720947a63ce1b9e399d2c068ff4
- stable/c/82f1d6042611d45b8b9de423bbcb4e0ced9ec62b