- 8.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 33 days later
· 33 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 8bc609999ec223089fec8d74c7de27d689606b36
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 62604376c313178811375f40a282fc2a46cd2311
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 8b98d662ab24f34710a56e03bc9169e4a5508606
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 22dfcc22c95e91295119a1c3b469816ce44c4804
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 121991d150735f3c0f7401678ce4d35c5b4ac898
- affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < f0772389413dce9657c7d6950abf3edbbd511356
- affected 4.4
- unaffected < 4.4
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/26de0d2d9a8d14c03e5ebb25fd68b5bfcd5ac366 (opens in a new tab)
- https://git.kernel.org/stable/c/8bc609999ec223089fec8d74c7de27d689606b36 (opens in a new tab)
- https://git.kernel.org/stable/c/62604376c313178811375f40a282fc2a46cd2311 (opens in a new tab)
- https://git.kernel.org/stable/c/8b98d662ab24f34710a56e03bc9169e4a5508606 (opens in a new tab)
- https://git.kernel.org/stable/c/22dfcc22c95e91295119a1c3b469816ce44c4804 (opens in a new tab)
- https://git.kernel.org/stable/c/121991d150735f3c0f7401678ce4d35c5b4ac898 (opens in a new tab)
- https://git.kernel.org/stable/c/f0772389413dce9657c7d6950abf3edbbd511356 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80532 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89932)Record last updated .