Linux
KVM: nVMX: Always flush vpid02 on first use
In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Always flush vpid02 on first use Make sure vpid02 is always flushed on first use by setting last_vpid=0 when allocating vpid02. nested_vmx_transition_tlb_flush() will always detect a VPID change on first VM-Enter after VMXON, because VPID=0 in vmcs12 is not allowed if L1 enables VPID. This avoids using stale TLB entries from a previous lifetime of the VPID, that might have been associated with a different vCPU (or a completely different VM). Note that last_vpid is already being initialized as 0 when the vCPU is created, but it is not reset when vpid02 is freed on VMXOFF. Hence, the problem can only occur if L1 does VMXOFF -> VMXON, runs an L2, and KVM happens to reuse a VPID that has TLB entries on the physical CPU.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366
- >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 8bc609999ec223089fec8d74c7de27d689606b36
- >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 62604376c313178811375f40a282fc2a46cd2311
- >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 8b98d662ab24f34710a56e03bc9169e4a5508606
- >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 22dfcc22c95e91295119a1c3b469816ce44c4804
- >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 121991d150735f3c0f7401678ce4d35c5b4ac898
- >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < f0772389413dce9657c7d6950abf3edbbd511356
Fixed in 26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366, 8bc609999ec223089fec8d74c7de27d689606b36, 62604376c313178811375f40a282fc2a46cd2311, 8b98d662ab24f34710a56e03bc9169e4a5508606, 22dfcc22c95e91295119a1c3b469816ce44c4804, 121991d150735f3c0f7401678ce4d35c5b4ac898, f0772389413dce9657c7d6950abf3edbbd511356
- 4.4
Fixed in 0, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5, 7.3
Mitigation
Upgrade Linux to 26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366 or 8bc609999ec223089fec8d74c7de27d689606b36 or 62604376c313178811375f40a282fc2a46cd2311 or 8b98d662ab24f34710a56e03bc9169e4a5508606 or 22dfcc22c95e91295119a1c3b469816ce44c4804 or 121991d150735f3c0f7401678ce4d35c5b4ac898 or f0772389413dce9657c7d6950abf3edbbd511356 or later.
Upgrade Linux to 0 or 5.15.221 or 6.1.188 or 6.6.157 or 6.12.110 or 6.18.51 or 7.2.5 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.