CVE-2026-99631

Description

A flaw was found in the Linux kernel's AMD GPU (amdgpu) driver. This vulnerability allows a local user to cause a Denial of Service (DoS) through a task hang. When a process holding imported Direct Memory Access (DMA) buffers is abruptly terminated, the driver attempts to update page tables without verifying whether the virtual memory is ready, submitting requests to stopped entities.

Statement

This vulnerability is rated as Moderate severity because it requires local access on systems equipped with AMD graphics hardware and results solely in a denial of service without compromising data confidentiality or system integrity. An authenticated local user executing GPU workloads with shared memory buffers could cause a kernel task hang when the calling process is abruptly terminated. Systems lacking AMD graphics hardware or environments that do not load the amdgpu driver are not exposed.

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)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart

Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.

Frequently Asked Questions

Want to get errata notifications? Sign up here.