CVE-2026-97928
Description
A flaw was found in the AMD GPU (amdgpu) driver within the Linux kernel. When clearing video memory (VRAM) upon deallocation, the driver performs an unnecessary virtual memory flush operation. A local user can trigger this flaw during graphics memory operations, causing the graphics processing unit (GPU) engine to hang and resulting in a Denial of Service (DoS).
Statement
A flaw of Low impact was found in the AMD GPU (amdgpu) driver of the Linux kernel, affecting Red Hat Enterprise Linux 9 (from the 9.6 minor release onward), Red Hat Enterprise Linux 10, Red Hat In-Vehicle OS 2, and OpenShift Container Platform 4.19 and later versions that ship Red Hat Enterprise Linux CoreOS 9. During VRAM clear-on-release operations, the amdgpu_ttm_map_buffer() code path reaches video memory through its direct MC address without programming a GART window, yet the wipe still forces an unnecessary VMID 0 flush. On GFX11 hardware (such as Navi33) this spurious SDMA flush can wedge the GPU engine. A local user with access to the amdgpu graphics device and its render nodes can trigger this condition through ordinary graphics memory operations, causing the GPU engine to hang and resulting in a denial of service. The issue affects availability only; there is no impact on confidentiality or integrity.
Red Hat Enterprise Linux 7 and 8, earlier Red Hat Enterprise Linux 9 minor releases, and OpenShift Container Platform versions shipping kernels without the vulnerable code are not affected, because the affected code (introduced upstream in the 6.10 kernel DRM changes) is not present in those streams. While the CVSS:3.1 base score for this flaw is 5.5 (Moderate), Red Hat rates its impact as Low: exploitation requires local access to GPU render nodes on affected hardware, only the availability of the graphics subsystem is impacted, and no memory disclosure or corruption primitive is involved.
For the affected streams the fix is deferred: as a Low-severity, availability-only issue, it does not warrant an immediate out-of-cycle kernel update, and the upstream correction will be picked up through future regularly scheduled kernel updates. Until such an update ships, the residual risk is that a local user on systems with affected AMD GFX11 GPUs can wedge the GPU engine and hang graphics workloads until the system is recovered.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.