Strix
64.1K

CVE-2026-89932

HIGHCVSS 8.8/10

Last modified

CVE-2026-89932 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.

Description

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.

Metrics

CVSS 3.1
8.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366; >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 8bc609999ec223089fec8d74c7de27d689606b36; >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 62604376c313178811375f40a282fc2a46cd2311; >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 8b98d662ab24f34710a56e03bc9169e4a5508606; >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 22dfcc22c95e91295119a1c3b469816ce44c4804; >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < 121991d150735f3c0f7401678ce4d35c5b4ac898; >= 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0, < f0772389413dce9657c7d6950abf3edbbd511356
LinuxLinux4.4

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-89932?
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.
How severe is CVE-2026-89932?
CVE-2026-89932 has a CVSS score of 8.8/10 (HIGH severity).
How do I fix CVE-2026-89932?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-89932?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST