CVE-2026-80539

drm/amdgpu: disallow multiple FENCE chunks in one submit

N/A
Published: August 26, 2026 at 02:37 PM UTC
Updated: August 27, 2026 at 01:31 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.2 ≤ v < 6.1.1854.2 ≤ v < 6.12.1054.2 ≤ v < 6.18.464.2 ≤ v < 6.6.1534.2 ≤ v < 7.1.104.2 ≤ v < 7.24.2d38ceaf99ed015f2a0b9af3499791bd3a3daae21
Vendor states this is fixed in 070229262ede37d17c4ea596650deb6e5eb5d106 (fixed)
Vendor states this is fixed in 5f46322e0b84af29e10eb951ff45bd6ea40640de (fixed)
Vendor states this is fixed in 71aa45f7bfe46fbc6f51e7832573ff49b6005fea (fixed)
Vendor states this is fixed in 7e9954e7212042ec808b06181b365b14f00c6f0a (fixed)
Vendor states this is fixed in 931cd1d1baeae68e8eb2c23bc1f3d8934dca6241 (fixed)
Vendor states this is fixed in e3ee74d6dbbe409eb99546a7b0a02b2782f9021d (fixed)
Vendor states this is fixed in 4.2 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card