CVE announcement
Subject: CVE-2026-99312: KVM: x86: Unconditionally reset MMU context when emulating INIT
From: Greg Kroah-Hartman
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
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
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
The Linux kernel CVE team has assigned CVE-2026-99312 to this issue.
Issue introduced in 6.1 with commit ed129ec9057f89d615ba0c81a4984a90345a1684 and fixed in 6.12.118 with commit f55a3e4e08dc004b4bab7c1e9323d7e7e96e266a
Issue introduced in 6.1 with commit ed129ec9057f89d615ba0c81a4984a90345a1684 and fixed in 6.18.64 with commit 24f644ea26c2ebb7b14c3baa2aa92d37fde3095f
Issue introduced in 6.1 with commit ed129ec9057f89d615ba0c81a4984a90345a1684 and fixed in 7.3.5 with commit d47bae9eb33b3ca0843a0954b7d0cafb354c99b0
Issue introduced in 6.1 with commit ed129ec9057f89d615ba0c81a4984a90345a1684 and fixed in 7.4-rc2 with commit c7c288d178cb0b78d3464a616b16b1aa0b316049
Issue introduced in 5.15.81 with commit 6425c590d0cc6914658a630a40b7f8226aa028c3
Issue introduced in 6.0.11 with commit d40ef0a511676bd65ca9acb295430c07af59ab85
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
will be updated if fixes are backported, please check that for the most
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
