Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 55d7c22192becd0ec827a6901899ff56fa985658 – < 63912418f1fbb6456ea04bbcdf8f4d5090d23350
    • affected 55d7c22192becd0ec827a6901899ff56fa985658 – < 919e3e398bf301c6418dffdcd5e5c4fd9be39cf7
    • affected 55d7c22192becd0ec827a6901899ff56fa985658 – < 07c213f3499dd72e2922c1c73fe9ffea24874bef
    • affected 55d7c22192becd0ec827a6901899ff56fa985658 – < 1c9ba32308c02c198c378fcdf06be9ffc3111147
    • affected 55d7c22192becd0ec827a6901899ff56fa985658 – < eecfb76129ebef7e3aa41e18a4668cd91dfc6267
    • affected 55d7c22192becd0ec827a6901899ff56fa985658 – < 06dc892561f5a08b2493c34c8ec2cb94dea33159
    • affected 55d7c22192becd0ec827a6901899ff56fa985658 – < ccc42187fc2d0720947a63ce1b9e399d2c068ff4
    • affected 55d7c22192becd0ec827a6901899ff56fa985658 – < 82f1d6042611d45b8b9de423bbcb4e0ced9ec62b
  • Linux · Linux

    • affected 3.6
    • unaffected < 3.6
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74416 badge
[![CVE-2026-74416](https://cveledger.app/badge/CVE-2026-74416.svg)](https://cveledger.app/cve/CVE-2026-74416)

Record last updated .