CVE-2026-99711: KVM: nVMX: Process each host MSR entry at most once when unwinding failed VM-Entry
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 APICBASE triggers kvmrecalculateapicmap() 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.15 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.20 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
When can this issue be triggered?
It occurs when nested VMX VMLAUNCH or VMRESUME fails a VM-entry consistency check that hardware detects but KVM misses, causing KVM to unwind host MSR state.
What is the practical impact?
The faulty unwind path can process every matching MSR entry in the VM-exit load list, resulting in quadratic work. This is especially costly for MSRs that are expensive to emulate, such as APIC_BASE, whose writes trigger APIC map recalculation.
Are normal virtual machine managers likely to encounter this?
The description indicates the issue is likely moot for well-behaved VMMs, which are not expected to have multiple diverging entries in the relevant MSR load lists.