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.
https://git.kernel.org/stable/c/c33ef9d334059f7cb167569ed7b4779752fe4425
https://git.kernel.org/stable/c/6a4697ec81693f8db41a1c3ba81f3b9b2510879f
https://git.kernel.org/stable/c/42b98982aedf40f5076bf045bf359df4dea09468
https://git.kernel.org/stable/c/05fae367c6878d08f54a7c5bb6986a5e57e9bd1c