CVE-2026-99625
Description
A flaw was found in the Linux kernel's AMD GPU (amdgpu) driver. A local user could exploit this vulnerability to cause a Denial of Service (DoS) or memory corruption. When an error occurs while adding a task synchronization dependency (fence) to a scheduled job, the driver improperly releases the fence reference a second time. This duplicate release leads to reference counting errors that can result in a kernel crash.
Statement
This vulnerability is rated as Moderate severity for Red Hat Enterprise Linux because exploitation is restricted to local authenticated users on hardware utilizing AMD graphic devices. An attacker could trigger an error condition during GPU job dependency scheduling, causing an improper fence reference release and leading to a kernel crash. Environments that do not use AMD graphics hardware or do not load the amdgpu driver are not impacted.
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,Integrity
Technical Impact: DoS: Crash, Exit, or Restart
Integrity
Technical Impact: Modify Memory; Modify Application Data
Depending on the type of resource and the expected API behavior, this could lead to memory corruption, data corruption, or execution path corruption.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.