PoC Monitor
← All CVEs
CVE-2026-99312published 18 Nov 2026 08:42 UTCData: JSON · API

Linux

KVM: x86: Unconditionally reset MMU context when emulating INIT

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

First public PoC 2.2 daysafter publication · 20 Nov 2026
Public PoCs11 on GitHub
CVSS8.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= ed129ec9057f89d615ba0c81a4984a90345a1684, < f55a3e4e08dc004b4bab7c1e9323d7e7e96e266a
  • >= ed129ec9057f89d615ba0c81a4984a90345a1684, < 24f644ea26c2ebb7b14c3baa2aa92d37fde3095f
  • >= ed129ec9057f89d615ba0c81a4984a90345a1684, < d47bae9eb33b3ca0843a0954b7d0cafb354c99b0
  • >= ed129ec9057f89d615ba0c81a4984a90345a1684, < c7c288d178cb0b78d3464a616b16b1aa0b316049
  • 6425c590d0cc6914658a630a40b7f8226aa028c3
  • d40ef0a511676bd65ca9acb295430c07af59ab85
  • >= 5.15.81, < 5.16
  • >= 6.0.11, < 6.1

Fixed in f55a3e4e08dc004b4bab7c1e9323d7e7e96e266a, 24f644ea26c2ebb7b14c3baa2aa92d37fde3095f, d47bae9eb33b3ca0843a0954b7d0cafb354c99b0, c7c288d178cb0b78d3464a616b16b1aa0b316049, 5.16, 6.1

Linux Linux
  • 6.1

Fixed in 0, 6.12.118, 6.18.64, 7.3.5, 7.4-rc2

Mitigation

Upgrade Linux to f55a3e4e08dc004b4bab7c1e9323d7e7e96e266a or 24f644ea26c2ebb7b14c3baa2aa92d37fde3095f or d47bae9eb33b3ca0843a0954b7d0cafb354c99b0 or c7c288d178cb0b78d3464a616b16b1aa0b316049 or 5.16 or 6.1 or later.

Upgrade Linux to 0 or 6.12.118 or 6.18.64 or 7.3.5 or 7.4-rc2 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published18 Nov 2026 · t = 0First public PoC20 Nov 2026 · t+2.2d

First public PoC 2.2 days after publication; not in CISA KEV. First PoC: jmginer/pve-cve-2026-99312 (created 20 Nov 2026, found by us: 20 Nov 2026).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedFound by usStarsAssessment
jmginer/pve-cve-2026-99312 20 Nov 2026 +2.2 d 20 Nov 2026 0 PoC
Flags · score 15
  • no network code found (normal for a local exploit)

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.