Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Fixed version: Linux Linux 06dc892561f5a08b2493c34c8ec2cb94dea33159, 07c213f3499dd72e2922c1c73fe9ffea24874bef, 1c9ba32308c02c198c378fcdf06be9ffc3111147.

Low priority for now. Upgrade to Linux Linux 06dc892561f5a08b2493c34c8ec2cb94dea33159, 07c213f3499dd72e2922c1c73fe9ffea24874bef, 1c9ba32308c02c198c378fcdf06be9ffc3111147 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Nov 6, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74416

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.6affected
    • 55d7c22192becd0ec827a6901899ff56fa985658 and later · before 63912418f1fbb6456ea04bbcdf8f4d5090d23350affected · git
    • 55d7c22192becd0ec827a6901899ff56fa985658 and later · before 919e3e398bf301c6418dffdcd5e5c4fd9be39cf7affected · git
    • 55d7c22192becd0ec827a6901899ff56fa985658 and later · before 07c213f3499dd72e2922c1c73fe9ffea24874befaffected · git
    • 55d7c22192becd0ec827a6901899ff56fa985658 and later · before 1c9ba32308c02c198c378fcdf06be9ffc3111147affected · git
    • 55d7c22192becd0ec827a6901899ff56fa985658 and later · before eecfb76129ebef7e3aa41e18a4668cd91dfc6267affected · git
    • 55d7c22192becd0ec827a6901899ff56fa985658 and later · before 06dc892561f5a08b2493c34c8ec2cb94dea33159affected · git
    • 55d7c22192becd0ec827a6901899ff56fa985658 and later · before ccc42187fc2d0720947a63ce1b9e399d2c068ff4affected · git
    • 55d7c22192becd0ec827a6901899ff56fa985658 and later · before 82f1d6042611d45b8b9de423bbcb4e0ced9ec62baffected · git
    • before 3.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74412Aug 15, 2026 · wifi: rtw88: fix wrong pci_get_drvdata type in AER handlers
    35Monitor
  • ← EarlierCVE-2026-74413Aug 15, 2026 · wifi: rtw89: fix wrong pci_get_drvdata type in AER handlers
    35Monitor
  • Later →CVE-2026-74417Aug 15, 2026 · drm/radeon: fix integer overflow in radeon_align_pitch()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux06dc892561f5a08b2493c34c8ec2cb94dea33159Vendor (CNA)
Linux Linux07c213f3499dd72e2922c1c73fe9ffea24874befVendor (CNA)
Linux Linux1c9ba32308c02c198c378fcdf06be9ffc3111147Vendor (CNA)
Linux Linux63912418f1fbb6456ea04bbcdf8f4d5090d23350Vendor (CNA)
Linux Linux82f1d6042611d45b8b9de423bbcb4e0ced9ec62bVendor (CNA)
Linux Linux919e3e398bf301c6418dffdcd5e5c4fd9be39cf7Vendor (CNA)
Linux Linuxccc42187fc2d0720947a63ce1b9e399d2c068ff4Vendor (CNA)
Linux Linuxeecfb76129ebef7e3aa41e18a4668cd91dfc6267Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records