CVE-2026-99312
Description
A flaw was found in the Linux kernel's KVM (Kernel-based Virtual Machine) subsystem for x86 architectures. An attacker in a guest virtual machine could cause a Denial of Service (DoS) or memory corruption by triggering an INIT processor reset while nested virtualization is active. Because KVM fails to reset the Memory Management Unit (MMU) context when emulating an INIT signal with paging disabled, the hypervisor continues execution with stale memory mappings.
Statement
This vulnerability is rated as Moderate impact because successful exploitation requires nested virtualization on AMD-based KVM hosts and specific guest execution conditions, limiting the overall attack surface. A malicious actor with access to a nested guest could trigger processor reset emulation while memory paging is disabled, resulting in an inconsistent memory management unit state that leads to a denial of service. Standard virtualized environments without nested AMD virtualization, as well as Intel-based KVM deployments, are not affected.
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 | 5.6 | 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 | Changed | 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:C/C:N/I:N/A:H
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
If a resource is not initialized, it could contain unpredictable or expired data, or it could be initialized to defaults that are invalid. This can have security implications when the resource is expected to have certain properties or values.
Confidentiality
Technical Impact: Read Memory; Read Application Data
When reusing a resource such as memory or a program variable, the original contents of that resource may not be cleared before it is sent to an untrusted party.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.