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-68234drm/amdgpu: fix bo->pin leaking in amdgpu_bo_create_reserved

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix bo->pin leaking in amdgpu_bo_create_reserved amdgpu_bo_create_reserved() only allocates a new BO when *bo_ptr (struct amdgpu_bo **bo_ptr as input parameter) is NULL, it simply skips creation when *bo_ptr is non-NULL. But it unconditionally reserves, pins, gart allocates and maps the BO afterwards. When the same non-NULL BO pointer is passed in again, for example firmware buffers that live in adev and are re-loaded on every resume / cp_resume / start under AMDGPU_FW_LOAD_DIRECT, amdgpu_bo_pin() just increases pin_count unconditionally, however the matching teardown only unpins once, so pin_count never drops to zero, so TTM is not able to move, swap or evict a BO, causing BO leaks. This commit fixes this issue by only pinning the bo once at creation, and repeated calls no longer take additional pin references. (cherry picked from commit 3ddc0ae76202c447b6aec61e907b852bc94671cf)

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    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.18% · top 93% of all CVEs (18 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 53766e5adac75872e9d413cdbfd0e47ae40701f9 – < 7aea619d9f186dcf0f1289879e9edb69d2b56639
    • affected 53766e5adac75872e9d413cdbfd0e47ae40701f9 – < b572d0814c1366701ca704286589fab025802566
    • affected 53766e5adac75872e9d413cdbfd0e47ae40701f9 – < e06e0885725a16304b7723aeb478a78cca9dc96a
    • affected 53766e5adac75872e9d413cdbfd0e47ae40701f9 – < 51eeef1949c11d3dcb5f422a5d9b3f09ebe8a1bc
    • affected 53766e5adac75872e9d413cdbfd0e47ae40701f9 – < 2f390b4c83011452753fd84972f657d2b00a952b
    • affected 53766e5adac75872e9d413cdbfd0e47ae40701f9 – < ba7b6444097a73ccd3d3ac9e2be4ebb73d226460
    • affected 53766e5adac75872e9d413cdbfd0e47ae40701f9 – < 9743f60013273987abf415dc47474683d22aaee9
    • affected 53766e5adac75872e9d413cdbfd0e47ae40701f9 – < a2f895f3c852063258d62e9f74b081de07ca95df
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 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-68234 badge
[![CVE-2026-68234](https://cveledger.app/badge/CVE-2026-68234.svg)](https://cveledger.app/cve/CVE-2026-68234)

Record last updated .