CVE-2026-98342

Description

A flaw was found in the Linux kernel's Direct Memory Access (DMA) engine subsystem. A timing flaw allows a device structure to be freed from memory while active read operations are still referencing it. A local attacker could exploit this use-after-free race condition to cause a Denial of Service (DoS) by crashing the kernel or potentially gain elevated privileges.

Statement

A race between dma_issue_pending_all() and dma_device_release() can cause a reader to access a dma_device after the provider object has been removed from the global list and freed. The confirmed primitive is a use after free because list_del_rcu() was not followed by an RCU grace period before device_release() could call kfree(). A concurrent reader may dereference stale device fields or traverse stale channel data, causing a kernel crash and potentially creating memory corruption if the freed allocation is reused. For the CVSS the PR:L value represents the paranoid case where a restricted local service account, container root, or other delegated user can influence DMA provider teardown or device lifecycle operations. Typical systems require administrative privileges for driver unload or device removal, which is reflected by PR:H in the base score. The race requires a timing window between provider release and the RCU protected traversal, so AC:H is appropriate. The issue is not directly network reachable. Impact is at least a local denial of service via kernel crash and in the worst case may include confidentiality, integrity, and privilege escalation impact through reuse of the freed kernel object.

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 Score4.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/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:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.