CVE-2026-99312: KVM: x86: Unconditionally reset MMU context when emulating INIT
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 guestmode (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').
Affected Software
Event History
Frequently Asked Questions
Which KVM deployments are affected?
The issue affects nested SVM. It does not affect nested VMX, because INIT is unconditionally intercepted on VMX and therefore cannot be emulated while an L2 guest is active.
What guest state is required to trigger the issue?
An INIT must be emulated while an L2 guest is running with paging disabled (CR0.PG=0). In that case, KVM can resume L1 with a stale MMU context because the MMU page role includes the guest mode.
Does the affected condition require paging to be enabled?
No. The bug specifically occurs when INIT is emulated with paging already disabled in L2. The resolved change resets the MMU context unconditionally for emulated INIT, including states involving SMM.