FKIE_CVE-2026-99120
Vulnerability from fkie_nvd - Published: 2026-10-28 11:17 - Updated: 2026-10-28 11:17
Severity
Summary
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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/mmu.h",
"arch/x86/kvm/mmu/paging_tmpl.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "0caeefed99b37f03251a00eb1fdb403a1cf2cb68",
"status": "affected",
"version": "8db428fd5229ba509d515af10d7f33d7d4a54bfe",
"versionType": "git"
},
{
"lessThan": "d6e08ec2fff45e0ec69f11010851650d7c6282b9",
"status": "affected",
"version": "8db428fd5229ba509d515af10d7f33d7d4a54bfe",
"versionType": "git"
},
{
"lessThan": "e90ab3669181c6469e3647ef2b30ae408275f496",
"status": "affected",
"version": "8db428fd5229ba509d515af10d7f33d7d4a54bfe",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/mmu.h",
"arch/x86/kvm/mmu/paging_tmpl.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.18"
},
{
"lessThan": "6.18",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.59",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.13",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes\n\nWhen running Hyper-V from Windows 11, KVM is seeing the SS bit set\nin nested page fault error codes produced for shadowed NPT. The AMD\nmanual is unclear about when SS is set, including whether it can be set\nwhen SupervisorShadowStackEn (bit 6) is not set in the MISC_CTL field\nof the VMCB.\n\nNevertheless, the unexpected SS bit causes out of bounds accesses in\npermission_fault(), seen as either WARNs or UBSAN reports:\n\n kernel: UBSAN: array-index-out-of-bounds in arch/x86/kvm/mmu.h:225:27\n kernel: index 34 is out of range for type \u0027u16 [16]\u0027\n\n(in this case, the page fault error code is 34*2=0x44, i.e. SS|U; the\nreport shows SS|U|W happening as well). Fix the handling of unknown\nerror codes by dropping SS and (with a WARN) any bits not among those\nthat permission_fault() expects to receive.\n\nAt the same time, given the uncertainty about when hardware sets SS,\nfollow the processor\u0027s behavior when constructing the fault\u0027s error\ncode, and preserve the SS bit as passed to FNAME(walk_addr_generic).\nWhile the behavior is surprising, there\u0027s a possibility that Hyper-V\nexpects it (Hyper-V does not even enable CET unless it finds MBEC/GMET!),\nso retain the information when reflecting the fault to L1 instead of\nunconditionally discarding it.\n\nBisection shows that this started happening with commit 687ee95c1b6d (\"KVM:\nnSVM: enable GMET for guests\"), even though SHSTK was available to guests\nsince Linux 6.18. However, this is not because bit 1 of MISC_CTL (GMET)\nsomehow enables reporting the SS bit; rather, it\u0027s simply that Hyper-V\nnever uses CET unless GMET is also present. The WARN is reproducible\neven with gmet=0, with some hacking of kvm-unit-tests\u0027s cet.c testcase\nto ensure that the first access to the shadow stack triggers a page fault."
}
],
"id": "CVE-2026-99120",
"lastModified": "2026-10-28T11:17:31.613",
"metrics": {},
"published": "2026-10-28T11:17:31.613",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0caeefed99b37f03251a00eb1fdb403a1cf2cb68"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d6e08ec2fff45e0ec69f11010851650d7c6282b9"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e90ab3669181c6469e3647ef2b30ae408275f496"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…