CVE-2026-72095

Description

A flaw was found in the Linux kernel's dma-fence component. The dma_fence_dedup_array() function incorrectly handles zero-count input, leading to a memory corruption vulnerability. A local attacker could potentially exploit this by triggering specific conditions in the amdgpu_userq_wait_*() functions, which may cause a system crash or lead to further compromise.

Statement

This vulnerability is evaluated as having Moderate severity because exploitation is restricted to local authenticated users with access to modern GPU subsystems and primarily results in a system crash rather than remote compromise. In typical Red Hat environments, triggering the underlying dereference requires interaction with AMD GPU user queue interfaces, limiting the attack surface to systems equipped with matching graphics hardware. Furthermore, earlier platforms such as Red Hat Enterprise Linux 8 are not affected because the vulnerable code path is not present.

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 Score5.5N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Confidentiality,Integrity,Availability,Other

Technical Impact: Varies by Context; Read Application Data

Uninitialized variables usually contain junk, which can not be trusted for consistency. Depending on the context, uninitialized variables could lead to denial of service conditions, or modify control flow in unexpected ways. They could also contain sensitive information that could be leaked if the variable is used in output. In some cases, an attacker can "pre-initialize" the variable using previous actions - i.e., control the contents of the variable - which might enable code execution.

Availability

Technical Impact: Alter Execution Logic; Unexpected State

This can cause a race condition if a lock variable check passes when it should not.

Authorization,Other

Technical Impact: Varies by Context

Strings that are not initialized are especially dangerous, since many functions expect a null at the end -- and only at the end -- of a string.

Frequently Asked Questions

Want to get errata notifications? Sign up here.