Skip to content
Threat Brief

← All advisories

CVE-2026-99312

High 8.8No known exploitationFix available

KVM: x86: Unconditionally reset MMU context when emulating INIT

Record last updated

CVSS score

8.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 4% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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').

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 5.15.81 before 5.165.16CVE Program
LinuxLinuxfrom 6.0.11 before 6.16.1CVE Program
LinuxLinuxfrom ed129ec9057f89d615ba0c81a4984a90345a1684 before c7c288d178cb0b78d3464a616b16b1aa0b316049c7c288d178cb0b78d3464a616b16b1aa0b316049CVE Program
LinuxLinuxfrom ed129ec9057f89d615ba0c81a4984a90345a1684 before f55a3e4e08dc004b4bab7c1e9323d7e7e96e266af55a3e4e08dc004b4bab7c1e9323d7e7e96e266aCVE Program
LinuxLinuxfrom ed129ec9057f89d615ba0c81a4984a90345a1684 before 24f644ea26c2ebb7b14c3baa2aa92d37fde3095f24f644ea26c2ebb7b14c3baa2aa92d37fde3095fCVE Program
LinuxLinuxfrom ed129ec9057f89d615ba0c81a4984a90345a1684 before d47bae9eb33b3ca0843a0954b7d0cafb354c99b0d47bae9eb33b3ca0843a0954b7d0cafb354c99b0CVE Program
LinuxLinux6.1Not documentedCVE Program
LinuxLinux6425c590d0cc6914658a630a40b7f8226aa028c3Not documentedCVE Program
LinuxLinuxd40ef0a511676bd65ca9acb295430c07af59ab85Not documentedCVE Program
Microsoftazl3 kernel 6.6.161.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.1Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references