Skip to content
Threat Brief

← All advisories

CVE-2026-99711

Severity unknownNo known exploitationFix available

KVM: nVMX: Process each host MSR entry at most once when unwinding failed VM-Entry

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 4.14.113 before 4.154.15CVE Program
LinuxLinuxfrom 4.19.36 before 4.204.20CVE Program
LinuxLinuxfrom bd18bffca35397214ae68d85cf7203aca25c3c1d before 6a4697ec81693f8db41a1c3ba81f3b9b2510879f6a4697ec81693f8db41a1c3ba81f3b9b2510879fCVE Program
LinuxLinuxfrom bd18bffca35397214ae68d85cf7203aca25c3c1d before c33ef9d334059f7cb167569ed7b4779752fe4425c33ef9d334059f7cb167569ed7b4779752fe4425CVE Program
LinuxLinuxfrom bd18bffca35397214ae68d85cf7203aca25c3c1d before 05fae367c6878d08f54a7c5bb6986a5e57e9bd1c05fae367c6878d08f54a7c5bb6986a5e57e9bd1cCVE Program
LinuxLinuxfrom bd18bffca35397214ae68d85cf7203aca25c3c1d before 42b98982aedf40f5076bf045bf359df4dea0946842b98982aedf40f5076bf045bf359df4dea09468CVE Program
LinuxLinux05e788500b46cb3c45231ea51a3e4b36c2ccd3c0Not documentedCVE Program
LinuxLinux4.20Not documentedCVE Program
LinuxLinuxf35e2a685c8168cbe2b92def87b0c6c0d6b19152Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.20Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references