CVE-2026-80539
Received Received - Intake

Double FENCE Chunk Submission in AMDGPU

Publication date: 2026-08-26

Last updated on: 2026-08-26

Assigner: kernel.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)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-26
Last Modified
2026-08-26
Generated
2026-08-26
AI Q&A
2026-08-26
EPSS Evaluated
N/A
NVD
CVE-2026-80539
EUVD
EUVD-2026-66454

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
amd amdgpu *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel's AMDGPU driver allows a user to submit multiple FENCE chunks in a single command. The driver fails to reject duplicate FENCE chunks, causing a reference count leak. This leads to a buffer object (BO) leak that persists even after the process exits.

Detection Guidance

This vulnerability is specific to the Linux kernel's AMDGPU driver and requires kernel-level inspection. Detection involves checking for duplicate FENCE chunks in GPU submissions. Use commands like 'dmesg | grep amdgpu' to look for kernel logs indicating issues with fence handling. Kernel debugging tools like 'ftrace' or 'perf' may also help analyze GPU submission paths.

Impact Analysis

An attacker could exploit this to cause a memory leak in the kernel, potentially leading to resource exhaustion. This may result in system instability, crashes, or denial-of-service conditions on affected systems.

Mitigation Strategies

Apply the latest kernel updates or patches from your Linux distribution that address this AMDGPU issue. If no patch is available, consider disabling the AMDGPU driver or using a different GPU driver temporarily. Monitor vendor advisories for updates and test affected systems after applying fixes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-80539. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart