Skip to main content
Menu
CVEs

CVE

Linux kernel stale MMU context after INIT in KVM nested SVM

CVE-2026-99312EUVD-2026-128497Published Updated Summary written by a model

Exploited
No known exploitation
Fix
Fixed in 5.16, 6.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.16, 6.1.

Summary

The Linux kernel's KVM x86 code does not always reset the MMU context when emulating an INIT event, so the first-level guest hypervisor (L1) can keep running with a stale MMU context. The flaw only affects nested SVM setups.

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

cve.now Index

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 5.16, 6.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-99312 (KVM: x86: Unconditionally reset MMU context when emulating INIT), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99312 (entry last updated 2026-11-18):
Affected:
- Linux Linux: from 5.15.81, fixed in 5.16; from 6.0.11, fixed in 6.1
- Linux Linux: versions 6.1
Fixed versions: 5.16, 6.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99312 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99312 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/f55a3e4e08dc004b4bab7c1e9323d7e7e96e266a
- https://git.kernel.org/stable/c/24f644ea26c2ebb7b14c3baa2aa92d37fde3095f
- https://git.kernel.org/stable/c/d47bae9eb33b3ca0843a0954b7d0cafb354c99b0
- https://git.kernel.org/stable/c/c7c288d178cb0b78d3464a616b16b1aa0b316049
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99312
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99312"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Linux Linux

    From 5.15.81 · fixed in 5.16; From 6.0.11 · fixed in 6.1

  • Linux Linux

    6.1

Evidence 6

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-99312

Is CVE-2026-99312 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-99312?

Linux: from 5.15.81 before 5.16; from 6.0.11 before 6.1. Linux: version 6.1.Source: cve.now feed data

How do I fix CVE-2026-99312?

Upgrade to a fixed version: 5.16, 6.1.Source: cve.now feed data

More CVEs