{"id":"CVE-2026-89932","published":"2026-09-16T11:17:02.543","lastModified":"2026-09-17T10:17:05.073","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: nVMX: Always flush vpid02 on first use\n\nMake sure vpid02 is always flushed on first use by setting last_vpid=0\nwhen allocating vpid02.  nested_vmx_transition_tlb_flush() will always\ndetect a VPID change on first VM-Enter after VMXON, because VPID=0 in\nvmcs12 is not allowed if L1 enables VPID.\n\nThis avoids using stale TLB entries from a previous lifetime of the\nVPID, that might have been associated with a different vCPU (or a\ncompletely different VM).\n\nNote that last_vpid is already being initialized as 0 when the vCPU is\ncreated, but it is not reset when vpid02 is freed on VMXOFF. Hence, the\nproblem can only occur if L1 does VMXOFF -> VMXON, runs an L2, and KVM\nhappens to reuse a VPID that has TLB entries on the physical CPU.","cvssScore":8.8,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/121991d150735f3c0f7401678ce4d35c5b4ac898","tags":[]},{"url":"https://git.kernel.org/stable/c/22dfcc22c95e91295119a1c3b469816ce44c4804","tags":[]},{"url":"https://git.kernel.org/stable/c/26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366","tags":[]},{"url":"https://git.kernel.org/stable/c/62604376c313178811375f40a282fc2a46cd2311","tags":[]},{"url":"https://git.kernel.org/stable/c/8b98d662ab24f34710a56e03bc9169e4a5508606","tags":[]},{"url":"https://git.kernel.org/stable/c/8bc609999ec223089fec8d74c7de27d689606b36","tags":[]},{"url":"https://git.kernel.org/stable/c/f0772389413dce9657c7d6950abf3edbbd511356","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}