CVE-2026-99312

KVM: x86: Unconditionally reset MMU context when emulating INIT

Published Nov 18, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

KVM: x86: Unconditionally reset MMU context when emulating INIT

Force an MMU reset when emulating an INIT even if paging was already
disabled, as the MMU page role includes guest_mode (L2), i.e. an INIT while
L2 is running with CR0.PG=0 will result in KVM running L1 with a stale MMU
context.

Alternatively, the reset could be scoped strictly to paging being enabled
or L2 being active, but SMM is also encoded in the page role. Even though
it _should_ be impossible for the vCPU to be INIT'd while SMM is active,
there's zero value in not handling SMM. At that point, the only scenario
where KVM _doesn't_ need to reset the MMU context is on an INIT with the
vCPU running in Real Mode or Unpaged Protect Mode, and while INIT in those
modes is somewhat common, it's far from a hot path and re-initializing the
MMU is not expensive, especially when the role isn't changing (KVM elides
most of the re-configuration in that case).

Note, like the Fixes commit, this bug only affects nested SVM as INIT is an
unconditional intercept on VMX, i.e. it's impossible to emulate INIT while
L2 is active.

Temporarily keep the guest TLB flush when CR0.PG is being cleared even
though it is fully redundant with the flush that is emitted on all INIT
events (KVM itself only does RESET when a vCPU is being created, i.e. when
CR0.PG must be '0').

Analysis

AI-generated

Technical impact

The Linux kernel’s KVM module erroneously resets the MMU context unconditionally when emulating an INIT instruction, even when paging is disabled. This can leave the host’s level‑1 (L1) hypervisor running with a stale context that still references structures from a level‑2 (L2) guest. An attacker able to cause such an INIT from a nested VM can therefore gain access to or corrupt memory that belongs to the nested guest, leading to data leakage or privilege escalation between virtual machines.

Affected Systems

All Linux kernels that implement x86 nested SVM Virtualization. The flaw is present in any kernel version exposed to the nested SVM path, regardless of the specific kernel release, until the patch commit referenced in the advisory is applied.

Risk and Exploitability

No EPSS score or KEV listing is available, suggesting no known active exploitation. However, the bug requires control over the host or an untrusted guest capable of triggering an INIT on a nested VM, making the attack local to the virtualized environment. Because the flaw breaks isolation between VMs, the risk is significant for environments relying on nested virtualization, while it is less critical for deployments without nested SVM.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that includes the commit fixing the unconditional MMU reset bug (as referenced in the advisory).
  • If nested virtualization is unnecessary, disable nested SVM by setting the appropriate sysctl or kernel parameter (e.g., net.vmm.nested=0).
  • After applying the patch or disabling nested SVM, restart the hypervisor and any affected virtual machines to ensure all contexts are refreshed.

Generated by OpenCVE AI on November 18, 2026 at 23:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-200
CWE-284
Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Unconditionally reset MMU context when emulating INIT Force an MMU reset when emulating an INIT even if paging was already disabled, as the MMU page role includes guest_mode (L2), i.e. an INIT while L2 is running with CR0.PG=0 will result in KVM running L1 with a stale MMU context. Alternatively, the reset could be scoped strictly to paging being enabled or L2 being active, but SMM is also encoded in the page role. Even though it _should_ be impossible for the vCPU to be INIT'd while SMM is active, there's zero value in not handling SMM. At that point, the only scenario where KVM _doesn't_ need to reset the MMU context is on an INIT with the vCPU running in Real Mode or Unpaged Protect Mode, and while INIT in those modes is somewhat common, it's far from a hot path and re-initializing the MMU is not expensive, especially when the role isn't changing (KVM elides most of the re-configuration in that case). Note, like the Fixes commit, this bug only affects nested SVM as INIT is an unconditional intercept on VMX, i.e. it's impossible to emulate INIT while L2 is active. Temporarily keep the guest TLB flush when CR0.PG is being cleared even though it is fully redundant with the flush that is emitted on all INIT events (KVM itself only does RESET when a vCPU is being created, i.e. when CR0.PG must be '0').
Title KVM: x86: Unconditionally reset MMU context when emulating INIT
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-284

    Improper Access Control

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 18, 2026, 8:42 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Nov 18, 2026, 9:17 AM
Modified
Nov 18, 2026, 9:17 AM