KVM: nVMX: Service local TLB flushes on failed nested VM-Enter

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.

Timeline

Scores

EPSS (exploitation in 30 days)

0.19% · top 92% of all CVEs (12 Nov 2026)

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.3.

Affected products

• Linux · Linux

  • affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < b577a7cd6d984dd430af88ee1c9e03da71b73ee0
  • affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < c0c66cd575e31218da6a7d104c6ef80b0830b60c
  • affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 1025b938dc439b75c720a568a855a13eeb245686
  • affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 312cdb6d8940827dea63a7a52fb714a5049f06d1
  • affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < f74fccdf4f7fb0780cd84944108d35f3d9dc46a7
  • affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < c43563e7518e65ec6ccaa6a65f84c5af5ca5d379
  • affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 62c3ee4c9f0e2efef5157358b3549e50ede96d73
  • affected 5c614b3583e7b6dab0c86356fa36c2bcbb8322a0 – < 05a0b701d1089fb57beeb8982f23c3bbafe0fa8b

• Linux · Linux

  • affected 4.4
  • unaffected < 4.4
  • unaffected 5.10.273 – ≤ 5.10.*
  • 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 – ≤ *

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-80530 (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

[![CVE-2026-89930](https://cveledger.app/badge/CVE-2026-89930.svg)](https://cveledger.app/cve/CVE-2026-89930)

Record last updated 30 Oct 2026, 12:33 UTC.