CVE-2026-99711: Linux kernel · KVM: nVMX: Process each host MSR entry at most once when unwinding failed VM-Entry
Source GCVE Database
Not known to be exploited · fixed in c33ef9d334059f7cb167569ed7b4779752fe4425 : update Linux kernel when convenient.
Data as of 20 Nov 2026, 07:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in c33ef9d334059f7cb167569ed7b4779752fe4425, 42b98982aedf40f5076bf045bf359df4dea09468, 6a4697ec81693f8db41a1c3ba81f3b9b2510879f +3
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99711 (opens in a new tab)
- git.kernel.org/stable/c/05fae367c6878d08f54a7c5bb6986a5e57e9bd1c (opens in a new tab)
- git.kernel.org/stable/c/42b98982aedf40f5076bf045bf359df4dea09468 (opens in a new tab)
- git.kernel.org/stable/c/6a4697ec81693f8db41a1c3ba81f3b9b2510879f (opens in a new tab)
- git.kernel.org/stable/c/c33ef9d334059f7cb167569ed7b4779752fe4425 (opens in a new tab)