# CVE-2026-74416: drm/radeon: fix memory leak in radeon_ring_restore() on lock failure

> A memory leak in the Radeon GPU driver during failed resets can exhaust kernel memory, leading to denial of service for local attackers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-74416, DEBIAN-CVE-2026-74416, GHSA-ccv2-c43x-5r5p, UBUNTU-CVE-2026-74416

## What is CVE-2026-74416?

CVE-2026-74416 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-74416?


## How do I fix CVE-2026-74416?

Apply the vendor's patch.

## Is CVE-2026-74416 being exploited?

There is no known exploitation of CVE-2026-74416 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74416 and fix it if it is affected.

What it is: CVE-2026-74416 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74416 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74416/ (Markdown: https://insights.sbomify.com/CVE-2026-74416/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74416
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74416
- OSV: https://osv.dev/vulnerability/CVE-2026-74416

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74416/
Summaries are generated and may contain mistakes; the official description above is the record.