Answer in brief
CVE-2026-89932 records a Unknown severity vulnerability in KVM: nVMX: Always flush vpid02 on first use. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8bc609999ec223089fec8d74c7de27d689606b36 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <62604376c313178811375f40a282fc2a46cd2311 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8b98d662ab24f34710a56e03bc9169e4a5508606 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <22dfcc22c95e91295119a1c3b469816ce44c4804 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <121991d150735f3c0f7401678ce4d35c5b4ac898 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f0772389413dce9657c7d6950abf3edbbd511356 || >=0 <5.15.221 || >=0 <6.1.188 || >=0 <6.6.157 || >=0 <6.12.110 || >=0 <6.18.51 || >=0 <7.2.5 | 26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366, 8bc609999ec223089fec8d74c7de27d689606b36, 62604376c313178811375f40a282fc2a46cd2311, 8b98d662ab24f34710a56e03bc9169e4a5508606, 22dfcc22c95e91295119a1c3b469816ce44c4804, 121991d150735f3c0f7401678ce4d35c5b4ac898, f0772389413dce9657c7d6950abf3edbbd511356, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5 |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.