drm/amdgpu: disallow multiple FENCE chunks in one submit (CVE-2026-80539) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80539

drm/amdgpu: disallow multiple FENCE chunks in one submit

Answer in brief

CVE-2026-80539 records a Unknown severity vulnerability in drm/amdgpu: disallow multiple FENCE chunks in one submit. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 26, 2026Updated Aug 26, 2026Source checked Aug 26, 2026First seen by HOL Aug 26, 2026Material review Aug 26, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <070229262ede37d17c4ea596650deb6e5eb5d106 \|\| >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <5f46322e0b84af29e10eb951ff45bd6ea40640de \|\| >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <71aa45f7bfe46fbc6f51e7832573ff49b6005fea \|\| >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <e3ee74d6dbbe409eb99546a7b0a02b2782f9021d \|\| >=d38ceaf99ed015f2a0b9af3499791bd3a3daae21 <931cd1d1baeae68e8eb2c23bc1f3d8934dca6241	070229262ede37d17c4ea596650deb6e5eb5d106, 5f46322e0b84af29e10eb951ff45bd6ea40640de, 71aa45f7bfe46fbc6f51e7832573ff49b6005fea, e3ee74d6dbbe409eb99546a7b0a02b2782f9021d, 931cd1d1baeae68e8eb2c23bc1f3d8934dca6241
Linux/Linuxgeneric	4.2	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 070229262ede37d17c4ea596650deb6e5eb5d106 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 26, 2026

Sources and claim methodology

Upstream source 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)

Quoted source text, attributed separately from HOL analysis.