CVE-2026-74416

drm/radeon: fix memory leak in radeon_ring_restore() on lock failure

N/A
Published: August 15, 2026 at 05:59 AM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.6 ≤ v < 5.10.2613.6 ≤ v < 5.15.2123.6 ≤ v < 6.1.1783.6 ≤ v < 6.12.973.6 ≤ v < 6.18.403.6 ≤ v < 6.6.1453.6 ≤ v < 7.1.53.6 ≤ v < 7.23.655d7c22192becd0ec827a6901899ff56fa985658
Vendor states this is fixed in 06dc892561f5a08b2493c34c8ec2cb94dea33159 (fixed)
Vendor states this is fixed in 07c213f3499dd72e2922c1c73fe9ffea24874bef (fixed)
Vendor states this is fixed in 1c9ba32308c02c198c378fcdf06be9ffc3111147 (fixed)
Vendor states this is fixed in 63912418f1fbb6456ea04bbcdf8f4d5090d23350 (fixed)
Vendor states this is fixed in 82f1d6042611d45b8b9de423bbcb4e0ced9ec62b (fixed)
Vendor states this is fixed in 919e3e398bf301c6418dffdcd5e5c4fd9be39cf7 (fixed)
Vendor states this is fixed in ccc42187fc2d0720947a63ce1b9e399d2c068ff4 (fixed)
Vendor states this is fixed in eecfb76129ebef7e3aa41e18a4668cd91dfc6267 (fixed)
Vendor states this is fixed in 3.6 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card