CVE-2026-99148

Description

A flaw was found in the Linux kernel's AMD GPU driver (amdgpu). When closing a handle to a shared graphics buffer object, the driver prematurely detaches its eviction fence before verifying whether active references remain. A local user could exploit this vulnerability to trigger the premature eviction of in-use memory while GPU user queues are still accessing it, leading to memory corruption or a Denial of Service (DoS) via a system crash.

Statement

amdgpu_gem_object_close detached the user queue eviction fence when any GEM handle was closed even though another handle could still retain the bo_va and its GPU mappings. The BO could then be evicted lacking suspension of the file user queues, allowing GPU access through mappings that were only marked for update. For the CVSS the PR:L value is selected because an attacker needs local access to the AMDGPU DRM interface and control of a user queue and GEM handles. AC:H reflects the need for duplicate handles, BO eviction, supported hardware and user queue behavior, and a useful timing window. Base C:N and I:N are used because the patch does not establish an information leak or write primitive. The paranoid score uses C:L and I:L because a stale GPU mapping may continue to reference VRAM after movement or reuse, while A:H covers a plausible GPU hang or reset affecting other workloads.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

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 Score6.6N/A7
Attack VectorLocalN/ALocal
Attack ComplexityLowN/AHigh
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityLowN/AHigh
Integrity ImpactLowN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H

cve.org: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.