CVE-2026-99699
Description
A flaw was found in the Linux kernel's Contiguous Memory Allocator (CMA). On confidential virtual machines requiring memory acceptance, multi-range CMA memory areas are reserved without being accepted before being released to the memory allocator. When the system or a local user accesses an unaccepted page, a fatal error is triggered, leading to a kernel crash and a Denial of Service (DoS).
Statement
This vulnerability is rated as Moderate severity because exploitation is limited to a local denial of service and requires specialized virtualization environments utilizing confidential computing technologies like Intel TDX or AMD SEV-SNP. The issue only manifests when multi-range contiguous memory allocation is configured within these confidential guest virtual machines. Standard bare-metal deployments and typical virtualization environments without memory acceptance mechanisms are unaffected by this condition.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.7 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/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)
Confidentiality
Technical Impact: Read Memory; Read Application Data
When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability
The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.
Other
Technical Impact: Unexpected State; Varies by Context
The consequences vary depending on the type of resource and how it is used within the product.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.