CVE-2026-99619
Description
A flaw was found in the Linux kernel's AMD GPU driver. This vulnerability allows a local user to cause a denial of service (DoS) by crashing the operating system. When processing graphics command submissions, an error encountered while registering a job dependency causes the driver to release an internal synchronization reference twice. This premature release leads to an invalid memory access and a kernel crash when the resource is later referenced.
Statement
This vulnerability is rated as Moderate impact because exploitation is constrained to authenticated local users with access to AMD graphics hardware interfaces, resulting strictly in a denial of service through a kernel crash. To trigger the flaw, an error during dependency scheduling must occur while handling multi-job command submissions, leading to an improper reference decrement. Systems lacking AMD GPU hardware or environments where untrusted users lack permissions to access GPU rendering nodes are not exposed to this risk.
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 | 4.7 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | 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:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing an error that causes the product to crash or exit out of its current operation.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.