Go to homepageCyberStrike

Menu

Star on GitHub · 3.4k
Sign inDownload

CVE-2026-89932

8.8 · HIGH

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 allocat…

Published Sep 16, 2026EPSS 0.17%

Overview

CVE-2026-89932 is a high-severity vulnerability. It was published on September 16, 2026 and has a CVSS 3.1 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/121991d150735f3c0f7401678ce4d35c5b4ac898Refgit.kernel.org/stable/c/22dfcc22c95e91295119a1c3b469816ce44c4804Refgit.kernel.org/stable/c/26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366Refgit.kernel.org/stable/c/62604376c313178811375f40a282fc2a46cd2311Refgit.kernel.org/stable/c/8b98d662ab24f34710a56e03bc9169e4a5508606Refgit.kernel.org/stable/c/8bc609999ec223089fec8d74c7de27d689606b36Refgit.kernel.org/stable/c/f0772389413dce9657c7d6950abf3edbbd511356

How CyberStrike helps

Frequently asked questions

What is CVE-2026-89932?

CVE-2026-89932 is a high-severity vulnerability. It was published on September 16, 2026 and has a CVSS 3.1 base score of 8.8 (HIGH).

How severe is CVE-2026-89932?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-89932?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-89932?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-89932 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999
LiveWatch live →