Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99312KVM: x86: Unconditionally reset MMU context when emulating INIT

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

  1. ID reserved

    By Linux

  2. · 54 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
Not scored

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ed129ec9057f89d615ba0c81a4984a90345a1684 – < f55a3e4e08dc004b4bab7c1e9323d7e7e96e266a
    • affected ed129ec9057f89d615ba0c81a4984a90345a1684 – < 24f644ea26c2ebb7b14c3baa2aa92d37fde3095f
    • affected ed129ec9057f89d615ba0c81a4984a90345a1684 – < d47bae9eb33b3ca0843a0954b7d0cafb354c99b0
    • affected ed129ec9057f89d615ba0c81a4984a90345a1684 – < c7c288d178cb0b78d3464a616b16b1aa0b316049
    • affected 6425c590d0cc6914658a630a40b7f8226aa028c3
    • affected d40ef0a511676bd65ca9acb295430c07af59ab85
    • affected 5.15.81 – < 5.16
    • affected 6.0.11 – < 6.1
  • Linux · Linux

    • affected 6.1
    • unaffected < 6.1
    • unaffected 6.12.118 – ≤ 6.12.*
    • unaffected 6.18.64 – ≤ 6.18.*
    • unaffected 7.3.5 – ≤ 7.3.*
    • unaffected 7.4-rc2 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99312 badge
[![CVE-2026-99312](https://cveledger.app/badge/CVE-2026-99312.svg)](https://cveledger.app/cve/CVE-2026-99312)

Record last updated .