CVE-2026-80539

drm/amdgpu: disallow multiple FENCE chunks in one submit

State
Published
Severity
Not scored
Published
Aug 26, 2026
Updated
Aug 27, 2026
Reserved
Aug 26, 2026

Read the record on cve.org

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)

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 7e9954e7212042ec808b06181b365b14f00c6f0aAffected
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 070229262ede37d17c4ea596650deb6e5eb5d106Affected
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 5f46322e0b84af29e10eb951ff45bd6ea40640deAffected
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 71aa45f7bfe46fbc6f51e7832573ff49b6005feaAffected
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before e3ee74d6dbbe409eb99546a7b0a02b2782f9021dAffected
  • d38ceaf99ed015f2a0b9af3499791bd3a3daae21 to before 931cd1d1baeae68e8eb2c23bc1f3d8934dca6241Affected
LinuxLinux
  • 4.2Affected
  • before 4.2Not affected
  • 6.1.185 through 6.1.*Not affected
  • 6.6.153 through 6.6.*Not affected
  • 6.12.105 through 6.12.*Not affected
  • 6.18.46 through 6.18.*Not affected
  • 7.1.10 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.