CVE-2026-99312
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').
Timeline
- 2026-11-18Published by the CNA08:42 UTC
- 2026-11-18Published in NVD09:17 UTC · 35 minutes after the CNA
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| linux linux | from 5.15.81 before 5.16fixed in 5.16from 6.0.11 before 6.1fixed in 6.1 | 5.166.1 |
| linux linux_kernel | from 6.1 before 6.12.118fixed in 6.12.118from 6.1 before 6.18.64fixed in 6.18.64from 6.1 before 7.3.5fixed in 7.3.5from 6.1 before 7.4-rc2fixed in 7.4-rc2from 5.15.81no fix listed(+1 more) | 6.12.1186.18.647.3.57.4-rc2not listed |
References
- https://git.kernel.org/stable/c/24f644ea26c2ebb7b14c3baa2aa92d37fde3095f
- https://git.kernel.org/stable/c/c7c288d178cb0b78d3464a616b16b1aa0b316049
- https://git.kernel.org/stable/c/d47bae9eb33b3ca0843a0954b7d0cafb354c99b0
- https://git.kernel.org/stable/c/f55a3e4e08dc004b4bab7c1e9323d7e7e96e266a
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-99312'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-99312'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-99312'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-99312'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).