CVE-2026-99120

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-112020 (ENISA EUVD) · GHSA-r4wm-h5f5-6qhj (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

KVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes

When running Hyper-V from Windows 11, KVM is seeing the SS bit set in nested page fault error codes produced for shadowed NPT. The AMD manual is unclear about when SS is set, including whether it can be set when SupervisorShadowStackEn (bit 6) is not set in the MISC_CTL field of the VMCB.

Nevertheless, the unexpected SS bit causes out of bounds accesses in permission_fault(), seen as either WARNs or UBSAN reports:

kernel: UBSAN: array-index-out-of-bounds in arch/x86/kvm/mmu.h:225:27 kernel: index 34 is out of range for type 'u16 [16]'

(in this case, the page fault error code is 34*2=0x44, i.e. SS|U; the report shows SS|U|W happening as well). Fix the handling of unknown error codes by dropping SS and (with a WARN) any bits not among those that permission_fault() expects to receive.

At the same time, given the uncertainty about when hardware sets SS, follow the processor's behavior when constructing the fault's error code, and preserve the SS bit as passed to FNAME(walk_addr_generic). While the behavior is surprising, there's a possibility that Hyper-V expects it (Hyper-V does not even enable CET unless it finds MBEC/GMET!), so retain the information when reflecting the fault to L1 instead of unconditionally discarding it.

Bisection shows that this started happening with commit 687ee95c1b6d ("KVM: nSVM: enable GMET for guests"), even though SHSTK was available to guests since Linux 6.18. However, this is not because bit 1 of MISC_CTL (GMET) somehow enables reporting the SS bit; rather, it's simply that Hyper-V never uses CET unless GMET is also present. The WARN is reproducible even with gmet=0, with some hacking of kvm-unit-tests's cet.c testcase to ensure that the first access to the shadow stack triggers a page fault.

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 28, 2026

Last Modified

October 28, 2026

Vendor Advisories for CVE-2026-99120(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (192 versions)
  • every version up to 7.2.13-1: fixed in 7.2.13-1
—

Data Freshness Timeline

(refreshed 5× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-11-13 16:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-11-08 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-11-08 09:04 UTCEchelonGraph re-scored
  15. 2026-11-08 09:04 UTCGHSA enrichmentGHSA-r4wm-h5f5-6qhj
  16. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-28 11:26 UTCNVD update
Show 3 more
  1. 2026-10-28 11:01 UTCENISA EUVD ID recordedEUVD-2026-112020 · Source: ENISA EUVD
  2. 2026-10-28 10:47 UTCEchelonGraph re-scored
  3. 2026-10-28 10:44 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-99120?
CVE-2026-99120 is a vulnerability whose severity is not yet rated; its CVE record was published on October 28, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes When running Hyper-V from Windows 11, KVM is seeing the SS bit set in nested page fault error codes produced for shadowed NPT. The AMD manual is unclear about when SS…
When was the CVE record for CVE-2026-99120 published?
The CVE record for CVE-2026-99120 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 28, 2026; the record at its source may have been updated since.
Is CVE-2026-99120 actively exploited?
CVE-2026-99120 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-99120?
A fix for CVE-2026-99120 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99120 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-99120

Explore →

Is Your Infrastructure Affected by CVE-2026-99120?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.