CVE-2026-99630
Description
A flaw was found in the Linux kernel's AMD GPU driver. A local user could cause a Denial of Service (DoS) by triggering conditions where graphics memory allocations are evicted and subsequently restored. Because the driver fails to properly validate and lock moved individual buffer objects during user queue restoration, the graphics processor attempts to access invalid memory addresses, resulting in queue faults and a system crash.
Statement
This vulnerability is rated as Moderate severity because exploitation is restricted to authenticated local users on systems equipped with supported AMD graphics hardware. Under specific memory eviction scenarios involving user queue virtual machines, the graphics driver can encounter an unhandled queue fault, resulting in a denial of service. The issue does not permit remote access, data modification, or unauthorized disclosure of confidential information.
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
Understanding the Weakness (CWE)
Integrity,Availability
Technical Impact: Modify Application Data; DoS: Instability; DoS: Crash, Exit, or Restart
When a resource is not properly locked, an attacker could modify the resource while it is being operated on by the product. This might violate the product's assumption that the resource will not change, potentially leading to unexpected behaviors.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.