KVM: nVMX: Always flush vpid02 on first use
Published Sep 16, 2026
8.8
HIGHCVSS 3.1
EPSS 0.18%
Description
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 products
-
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version StatusaffectedConstraints
- Version
-
- Version 4.4StatusaffectedConstraints-
- Version 0StatusunaffectedConstraints<4.4
- Version 5.15.221StatusunaffectedConstraints<=5.15.*
- Version 6.1.188StatusunaffectedConstraints<=6.1.*
- Version 6.12.110StatusunaffectedConstraints<=6.12.*
- Version 6.18.51StatusunaffectedConstraints<=6.18.*
- Version 6.6.157StatusunaffectedConstraints<=6.6.*
- Version 7.2.5StatusunaffectedConstraints<=7.2.*
- Version 7.3-rc1StatusunaffectedConstraints<=*
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux | unaffected |
| ||||||||||||||||||||||||||||||
| Linux | Linux | affected |
|
No data.
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
No remediation recorded yet.
No CWE recorded.
References (8)
- https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-80532 Advisory
- https://git.kernel.org/stable/c/121991d150735f3c0f7401678ce4d35c5b4ac898
- https://git.kernel.org/stable/c/22dfcc22c95e91295119a1c3b469816ce44c4804
- https://git.kernel.org/stable/c/26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366
- https://git.kernel.org/stable/c/62604376c313178811375f40a282fc2a46cd2311
- https://git.kernel.org/stable/c/8b98d662ab24f34710a56e03bc9169e4a5508606
- https://git.kernel.org/stable/c/8bc609999ec223089fec8d74c7de27d689606b36
- https://git.kernel.org/stable/c/f0772389413dce9657c7d6950abf3edbbd511356
Change history (0)
No recorded changes yet.