CVE-2026-99627

Description

A flaw was found in the AMD GPU (amdgpu) driver within the Linux kernel. A local user could cause a denial of service (DoS) or system instability when submitting GPU workloads while the graphics processing engine is in a power-saving state. Because the driver fails to keep the graphics engine powered while updating performance monitoring configuration registers, the updates fail to apply. Consequently, GPU tasks execute with incorrect memory identifiers, resulting in GPU memory page faults.

Statement

This vulnerability is rated as Moderate impact because exploitation is constrained to a local denial of service and requires systems equipped with specialized AMD GFX12 hardware. An authenticated local user submitting workloads to the graphics interface can trigger GPU memory page faults and device hangs due to improper power management during performance monitor configuration. Standard server environments without dedicated AMD graphics processors or configurations where access to direct rendering nodes is restricted remain unaffected.

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 HatNVDcve.org
Base Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/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,Confidentiality,Other

Technical Impact: Modify Application Data; Read Application Data; Alter Execution Logic

If access to a shared resource is not synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.

Frequently Asked Questions

Want to get errata notifications? Sign up here.