VulnTideExploited vulnerabilities, by vendor. Data as of .
Not in CISA KEVPublished CVSS 9.3 criticalEPSS 0.2% probability of exploitation in 30 days
Linux

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

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of . If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?
0.2%

EPSS score, percentile 8.1 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?
9.3 Critical

CVSS v3.1 base score, given by the CNA

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

The CVE record links no vendor advisory, patch or mitigation.

Which versions are affected?

Affected

  • 4.4

Unaffected before 4.4; 5.15.221; 6.1.188; 6.6.157; 6.12.110; 6.18.51; and 2 more

Versions by product

Source: CISA KEV 2026.10.28, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.

What to do

Advisories and patches

The CVE record links no vendor advisory, patch or mitigation.

This summary is based on the CVE record as of . Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

As listed in the CVE record.

Linux Linux
StatusVersions
Affectedfrom 5c614b3583e7 to before c0c66cd575e3
Affectedfrom 5c614b3583e7 to before 1025b938dc43
Affectedfrom 5c614b3583e7 to before 312cdb6d8940
Affectedfrom 5c614b3583e7 to before f74fccdf4f7f
Affectedfrom 5c614b3583e7 to before c43563e7518e
Affectedfrom 5c614b3583e7 to before 62c3ee4c9f0e
Affectedfrom 5c614b3583e7 to before 05a0b701d108

Versions not listed are: unaffected.

Linux Linux
StatusVersions
Affected4.4
Unaffectedbefore 4.4
Unaffected5.15.221
Unaffected6.1.188
Unaffected6.6.157
Unaffected6.12.110
Unaffected6.18.51
Unaffected7.2.5
Unaffected7.3

Versions not listed are: affected.

Versions the record lists as unaffected: 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5, 7.3.

Source: CVE List, as of . About the data.

About this vulnerability

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

Summary: CVE record, as of .

  • CISA has not added CVE-2026-89930 to its Known Exploited Vulnerabilities (KEV) catalog, as of 28 Oct 2026.
  • The CVE record was published on 16 Sep 2026.
  • The CVE record carries a CVSS v3.1 base score of 9.3 (Critical), given by its CNA.
  • FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.2% (percentile 8.1), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.

Source: CISA KEV 2026.10.28, as of ; CVE List, as of ; FIRST EPSS, as of . About the data.

Description

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

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.

Source: CVE List, as of . About the data.

Timeline

DateEvent
CVE record published
CVE record last updated

References

7

Known exploited Linux vulnerabilities

  • CVE-2026-46300: Linux Kernel Missing Initialization of a Variable Vulnerability (added )
  • CVE-2025-39682: Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability (added )
  • CVE-2025-39964: Linux Kernel Race Condition Vulnerability (added )
  • CVE-2026-53266: Linux Kernel Out-of-Bounds Write Vulnerability (added )
  • CVE-2026-53362: Linux Kernel Unspecified Vulnerability (added )