CVE-2026-99120: KVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
Vulnerability summary
CVE-2026-99120 is a low (CVSS 2.1) vulnerability in linux. EPSS estimates a 0.17% chance of exploitation in the next 30 days, higher than 7% of scored vulnerabilities.
Not severe (CVSS 2.1, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 5 · Related 4Timeline
- 28-10-2026PublishedVulnerability first disclosed.
Description
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 metrics
1 score · 1 source · 1 versionEPSS trend
Probability
0.17%
Chance of exploitation in the next 30 days
Percentile
7%
Versus all other CVEs
30-day change
Change unavailable
Change unavailable
Known exploited
Compare KEV catalogsNot in the CISA KEV catalog.
Not in the ENISA CNW catalog.
Not in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root causeNo weakness data has been published for this record.
Affected systems
Known conditions: local access, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu169 products
- linuxAll versions (No fix recorded) | < 7.3.0-10.10 | < 7.0.0-44.44
- linux-allwinner-5.19All versions (No fix recorded)
- linux-awsAll versions (No fix recorded) | < 7.3.0-1004.4 | < 7.0.0-1018.19
- linux-aws-5.0All versions (No fix recorded)
- linux-aws-5.11All versions (No fix recorded)
Debian1 product
- linuxAll versions (No fix recorded) | < 7.2.13-1
Linux1 product
- linux≥ 8db428fd5229ba509d515af10d7f33d7d4a54bfe, < 0caeefed99b37f03251a00eb1fdb403a1cf2cb68 | ≥ 8db428fd5229ba509d515af10d7f33d7d4a54bfe, < d6e08ec2fff45e0ec69f11010851650d7c6282b9 | ≥ 8db428fd5229ba509d515af10d7f33d7d4a54bfe, < e90ab3669181c6469e3647ef2b30ae408275f496 | 6.18
3 vendors · 171 products