KVM: nVMX: Process each host MSR entry at most once when unwinding failed VM-Entry
Summary
| CVE | CVE-2026-99711 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:18:07 UTC |
| Updated | 2026-11-20 06:18:07 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
KVM: nVMX: Process each host MSR entry at most once when unwinding failed VM-Entry
Add a missing "break" in the inner for-loop of the open coded mess that
unwinds MSRs back to the pre-VM-Enter state when VMLAUNCH/VMRESUME VM-Fails
due to a consistency check that is caught by hardware but missed by KVM.
I.e. move on to the next MSR in the VM-Entry load list after performing a
write using a value found in the VM-Exit load list. Processing *every*
matching entry in the VM-Exit load list makes the processing quadratic,
which is problematic if the load lists are full of MSRs that are expensive
to emulate. E.g. writing APIC_BASE triggers kvm_recalculate_apic_map() and
a whole pile of unnecessary work.
Functionally, arbitrarily restoring the value of the first matching entry
is "fine", because none of this is architecturally correct: the load lists
are never supposed to have been used in the first place. In practice, it's
likely a moot point as no well-behaved VMM will have multiple, diverging
entries in the load lists. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected bd18bffca35397214ae68d85cf7203aca25c3c1d 05fae367c6878d08f54a7c5bb6986a5e57e9bd1c git |
Not specified |
| CNA |
Linux |
Linux |
affected bd18bffca35397214ae68d85cf7203aca25c3c1d 42b98982aedf40f5076bf045bf359df4dea09468 git |
Not specified |
| CNA |
Linux |
Linux |
affected bd18bffca35397214ae68d85cf7203aca25c3c1d 6a4697ec81693f8db41a1c3ba81f3b9b2510879f git |
Not specified |
| CNA |
Linux |
Linux |
affected bd18bffca35397214ae68d85cf7203aca25c3c1d c33ef9d334059f7cb167569ed7b4779752fe4425 git |
Not specified |
| CNA |
Linux |
Linux |
affected 05e788500b46cb3c45231ea51a3e4b36c2ccd3c0 git |
Not specified |
| CNA |
Linux |
Linux |
affected f35e2a685c8168cbe2b92def87b0c6c0d6b19152 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.14.113 4.15 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 4.19.36 4.20 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 4.20 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.20 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.118 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.64 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3.5 7.3.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.4-rc2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/6a4697ec81693f8db41a1c3ba81f3b9b2510879f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/05fae367c6878d08f54a7c5bb6986a5e57e9bd1c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c33ef9d334059f7cb167569ed7b4779752fe4425 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/42b98982aedf40f5076bf045bf359df4dea09468 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.