CVE-2026-99645

Description

A flaw was found in the Linux kernel's Contiguous Memory Allocator (CMA). When memory is released while still in use by a device driver, the kernel prematurely returns the active memory pages to the system memory pool. This issue allows the same memory region to be assigned to multiple consumers or corrupts internal memory tracking structures. A local user triggering this behavior could cause memory corruption or a denial of service (DoS) through a system crash.

Statement

This vulnerability is rated as having Moderate impact because exploitation requires local system access and depends on race conditions during hardware DMA buffer teardown. In standard Red Hat Enterprise Linux environments, this issue only occurs if an underlying device driver attempts to release contiguous memory buffers prior to halting active DMA operations. While prematurely returning active memory back into the kernel allocator can cause memory corruption or a system crash, unprivileged local users cannot directly control or trigger this allocator behavior without specific driver interactions.

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 Score7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: 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 Application Data; Read Memory

If the released resource is subsequently reused or reallocated, then a read operation on the original resource might access sensitive data that is associated with a different user or entity.

Availability

Technical Impact: Unexpected State; DoS: Crash, Exit, or Restart

When the resource is released, the software might modify some of its structure, or close associated channels (such as a file descriptor). When the software later accesses the resource as if it is valid, the resource might not be in an expected state, leading to resultant errors that may lead to a crash.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands; Modify Application Data; Modify Memory

When the resource is released, the software might modify some of its structure. This might affect logic in the sections of code that still assume the resource is active. If the released resource is related to memory and is used in a function call, or points to unexpected data in a write operation, then code execution may be possible upon subsequent accesses.

Frequently Asked Questions

Want to get errata notifications? Sign up here.