Skip to content
statance
MenuClose
high · CVSS 8.8

CVE-2026-99312

KVM: x86: Unconditionally reset MMU context when emulating INIT

Published 18 Nov 2026 · Source updated 19 Nov 2026 · Retrieved 2026-11-19 14:23 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: ed129ec9057f89d615ba0c81a4984a90345a1684 to < f55a3e4e08dc004b4bab7c1e9323d7e7e96e266a; affected: ed129ec9057f89d615ba0c81a4984a90345a1684 to < 24f644ea26c2ebb7b14c3baa2aa92d37fde3095f; affected: ed129ec9057f89d615ba0c81a4984a90345a1684 to < d47bae9eb33b3ca0843a0954b7d0cafb354c99b0; affected: ed129ec9057f89d615ba0c81a4984a90345a1684 to < c7c288d178cb0b78d3464a616b16b1aa0b316049; affected: 6425c590d0cc6914658a630a40b7f8226aa028c3; affected: d40ef0a511676bd65ca9acb295430c07af59ab85; affected: 5.15.81 to < 5.16; affected: 6.0.11 to < 6.1See vendor advisory
LinuxLinuxaffected: 6.1; unaffected: 0 to < 6.1; unaffected: 6.12.118 to ≤ 6.12.*; unaffected: 6.18.64 to ≤ 6.18.*; unaffected: 7.3.5 to ≤ 7.3.*; unaffected: 7.4-rc2 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed