Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-99312Published 2026-11-18

CVE-2026-99312 — Linux

highPublic exploit1 PoC repo

As of 2026-11-20, CVE-2026-99312 is a HIGH-severity vulnerability in Linux, CVSS v3.1 8.8, EPSS 0.1% (4.4th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-99312, most recently “Linux KVM Flaw CVE-2026-99312 Lets Guest VMs Access Host Memory on AMD Hosts”.

CVSS v3.1
8.8/10High
EPSS
0.1%Higher than 4.4% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
6.6/10Threadlinqs triage score
Published
Updated 2026-11-20
CVSS v3.1 8.8 (HIGH) · EPSS 0.1% (higher than 4.4% of all scored CVEs) · Priority 6.6/10 · Published 2026-11-18

Last updated:

What is CVE-2026-99312?

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

Its CVSS v3 base vector states that the flaw requires local access to the host, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3 days ago.

Severity and exploitation probability

CVSS v3.1 base score
8.8 — HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 4.4% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
6.6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-11-18

Is CVE-2026-99312 being exploited?

Weaponised exploit code for CVE-2026-99312 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 44 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-99312

No vendor patch reference has been recorded for CVE-2026-99312 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-99312

1 tracked threat in the Threadlinqs corpus references CVE-2026-99312, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, public proof-of-concept repositories. This product uses the NVD API but is not endorsed or certified by the NVD.

Other references