CVE-2026-99698

Description

A flaw was found in the Linux kernel's Contiguous Memory Allocator (CMA). In confidential virtual machine environments, the operating system must explicitly validate and accept memory regions before accessing them. When a fixed CMA memory area is configured through kernel boot parameters, the kernel fails to accept the reserved memory. Accessing this unaccepted memory can cause a guest kernel crash, leading to a Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate severity because exploitation requires privileged administrative access to configure non-standard kernel boot parameters and is limited strictly to confidential virtual machine guests. Standard Red Hat Enterprise Linux configurations do not define fixed Contiguous Memory Allocator base addresses by default, substantially reducing exposure across typical installations. When triggered in confidential computing environments such as Intel TDX or AMD SEV-SNP, the failure to accept reserved physical memory results in a guest kernel panic, causing a denial of service confined entirely to the virtual machine without breaching hypervisor isolation.

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.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredHighN/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:H/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

Want to get errata notifications? Sign up here.