Menu

Star on GitHub · 3.2k

CVE-2026-74416

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 a…

Published Aug 15, 2026EPSS 0.22%

Overview

CVE-2026-74416 is a known-severity vulnerability. It was published on August 15, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-74416?

CVE-2026-74416 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-74416?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-74416?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-74416?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-74416 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.