drm/radeon: fix memory leak in radeon_ring_restore() on lock failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 55d7c22192becd0ec827a6901899ff56fa985658 · < 06dc892561f5a08b2493c34c8ec2cb94dea33159| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s Radeon driver leaks a ring backup buffer if a GPU reset fails while locking the ring. Repeated failures can exhaust kernel memory; the input does not establish an attacker path or access requirements.
Engineers running Linux systems that use the Radeon driver should check their kernel versions; affected versions were not provided.