AMDGPU Kernel Use-After-Free in User Queue Handling

Publication date: 2026-06-08

Last updated on: 2026-06-14

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: fix access to stale wptr mapping Use drm_exec to take both locks i.e vm root bo and wptr_obj bo to access the mapping data properly. This fixes the security issue of unmap the wptr_obj while a queue creation is in progress and passing other bo at same address. (cherry picked from commit 1fc6c8ab45dbee096469c08c13f6099d57a52d6c)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-08

Last Modified

2026-06-14

Generated

2026-06-29

AI Q&A

2026-06-08

EPSS Evaluated

2026-06-27

NVD

CVE-2026-46311

EUVD

EUVD-2026-35121

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's drm/amdgpu/userq component. It involves improper handling of access to a stale write pointer (wptr) mapping during queue creation. Specifically, the issue arises when the wptr_obj is unmapped while a queue creation is still in progress, and another buffer object (bo) is passed at the same address. The fix involves using drm_exec to take both necessary locks (vm root bo and wptr_obj bo) to properly access the mapping data and prevent this unsafe condition.

Impact Analysis

This vulnerability could lead to security issues related to improper memory access or data corruption within the graphics subsystem of the Linux kernel. Accessing stale mappings or passing incorrect buffer objects at the same address during queue creation might allow attackers to cause unexpected behavior, potentially leading to system instability or unauthorized access to memory.

Hi! I’m here to help you understand CVE-2026-46311. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70