CVE-2026-99343

Description

A flaw was found in the Linux kernel's KVM (Kernel-based Virtual Machine) subsystem. The x86 Memory Management Unit (MMU) page table walker does not properly verify that page table lookups remain within supported paging levels. A privileged guest user could exploit this condition during memory management operations to cause an out-of-bounds memory access on the host system. This failure can result in a host kernel crash, leading to a Denial of Service (DoS).

Statement

This vulnerability is rated Moderate because exploitation requires an authenticated, privileged user within an x86 virtual machine and is limited to causing a denial of service on the virtualization host. Red Hat virtualization environments are exposed only when hosting untrusted guest workloads where users have sufficient administrative privileges to manipulate guest page tables and trigger abnormal paging structures. Because the flaw does not facilitate arbitrary code execution or data leakage across tenant boundaries, the blast radius is confined to host availability.

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)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.