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-80539drm/amdgpu: disallow multiple FENCE chunks in one submit

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: disallow multiple FENCE chunks in one submit amdgpu_cs_pass1() dispatches on chunk_id once per chunk without rejecting repeated ids. p->uf_bo is a single-slot field, so a submission carrying two AMDGPU_CHUNK_ID_FENCE chunks runs amdgpu_cs_p1_user_fence() twice, and the second run overwrites p->uf_bo with a freshly referenced BO without dropping the reference taken by the first. amdgpu_cs_parser_fini() only unrefs the final p->uf_bo, so every FENCE chunk but the last leaks a BO reference. The leaked BO outlives handle close and process exit. Reject duplicate FENCE chunks the same way commit fec5f8e8c6bc ("drm/amdgpu: disallow multiple BO_HANDLES chunks in one submit") did for p->bo_list. (cherry picked from commit 665b1fc2a1845206408f9a2c6da67101789edb82)

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 1 day 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.17% · top 93% of all CVEs (17 Nov 2026)
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 d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 7e9954e7212042ec808b06181b365b14f00c6f0a
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 070229262ede37d17c4ea596650deb6e5eb5d106
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 5f46322e0b84af29e10eb951ff45bd6ea40640de
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 71aa45f7bfe46fbc6f51e7832573ff49b6005fea
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < e3ee74d6dbbe409eb99546a7b0a02b2782f9021d
    • affected d38ceaf99ed015f2a0b9af3499791bd3a3daae21 – < 931cd1d1baeae68e8eb2c23bc1f3d8934dca6241
  • Linux · Linux

    • affected 4.2
    • unaffected < 4.2
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.153 – ≤ 6.6.*
    • unaffected 6.12.105 – ≤ 6.12.*
    • unaffected 6.18.46 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .