CVE-2026-99312: KVM: x86: Unconditionally reset MMU context when emulating INIT
No distribution fix yet for RHEL 9/10, Ubuntu 22.04/24.04/26.04, Debian 12/13 · Affected: Linux · Exploitation: not established
At a glance
Higher than 8% of scored CVEs
What it isNVD
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').
Fix status by distribution
From each distribution’s security tracker. Distributions we did not check are not listed.
- Red Hat Enterprise Linux 10Affected, no fix releasedchecked 20 Nov 13:00 UTC
- Red Hat Enterprise Linux 9Affected, no fix releasedchecked 20 Nov 13:00 UTC
- Red Hat Enterprise Linux 8Not affectedchecked 20 Nov 13:00 UTC
- Ubuntu 26.04Affected, no fix releasedchecked 20 Nov 13:00 UTC
- Ubuntu 24.04Affected, no fix releasedchecked 20 Nov 13:00 UTC
- Ubuntu 22.04Affected, no fix releasedchecked 20 Nov 13:00 UTC
- Debian 13Affected, no fix releasedchecked 20 Nov 13:00 UTC
- Debian 12Affected, no fix releasedchecked 20 Nov 13:00 UTC
- SUSE Linux Enterprise Server 16.1Not affectedchecked 20 Nov 13:00 UTC
- SUSE Linux Enterprise Server 16.0Not affectedchecked 20 Nov 13:00 UTC
- SUSE Linux Enterprise Server 15 SP7Not affectedchecked 20 Nov 13:00 UTC
- openSUSE Leap 16.1Not affectedchecked 20 Nov 13:00 UTC
- openSUSE Leap 16.0Not affectedchecked 20 Nov 13:00 UTC
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.18 (18 Nov)
- Not establishedNothing in the sources we check
Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.
Weakness and public checks
- Public check
- No public nuclei template
Other CVEs in Linux
Every published CVE for Linux , by how far exploitation has gone. This one is among them.
What changed
Debian status tracked since 20 Nov 2026. Red Hat status tracked since 20 Nov 2026. SUSE status tracked since 20 Nov 2026. Ubuntu status tracked since 20 Nov 2026.
- Debian’s tracker lists Debian 12 as affected, with no fix released Debian
- Debian’s tracker lists Debian 13 as affected, with no fix released Debian
- Red Hat’s tracker lists RHEL 10 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 6 as not affected Red Hat
- Red Hat’s tracker lists RHEL 7 as not affected Red Hat
- Red Hat’s tracker lists RHEL 8 as not affected Red Hat
- Red Hat’s tracker lists RHEL 9 as affected, with no fix released Red Hat
- SUSE’s tracker lists openSUSE Leap 16.0 as not affected SUSE
- SUSE’s tracker lists openSUSE Leap 16.1 as not affected SUSE
- SUSE’s tracker lists SLES 12 SP5 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP1 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP2 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP3 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP4 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP5 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP6 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP7 as not affected SUSE
- SUSE’s tracker lists SLES 16.0 as not affected SUSE
- SUSE’s tracker lists SLES 16.1 as not affected SUSE
- Ubuntu’s tracker lists Ubuntu 14.04 as not affected Ubuntu
Showing the latest 20 changes.
Coverage1 article · 1 outlet
First in our coverage: The Hacker News, 20 Nov.
- Linux KVM flaw lets guest VMs read host memory on AMD systemsThe Hacker News · first in our coverage
New articles also arrive in the RSS feed.