Red Hot Cyber
Cybersecurity, Cybercrime News and Vulnerability Analysis

CVE-2026-89930

View the latest critical CVEs issued
This is a free service offered by Red Hot Cyber to the community. It allows you to view, on a single page, information about a single CVE from the National Vulnerability Database (NVD) and the National Institute of Standards and Technology (NIST) of the United States of America, the Forum of Incident Response and Security Teams (FIRST) regarding the EPSS score and percentile, data from the KEV catalog of the Cybersecurity and Infrastructure Security Agency (CISA), as well as selected resources from Red Hot Cyber and other international sources.

National Vulnerability Database Information

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.

CVSS Base Score: 9.3 (v3.1)

The CVSS Base Score is a score from 0 to 10 that represents the intrinsic severity of a vulnerability. A higher score indicates greater severity.

Value
0.02.55.07.510.0
Published on: 09/16/2026 11:17:02
Last modified: 09/16/2026 15:18:18
NIST: CVE source from the National Vulnerability Database (NVD)

CVSS Metrics Details

  • Base Severity: CRITICAL
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
  • Attack Vector: LOCAL
  • Attack Complexity: LOW
  • Privileges Required: NONE
  • User Interaction: NONE
  • Scope: CHANGED
  • Confidentiality Impact: HIGH
  • Integrity Impact: HIGH
  • Availability Impact: HIGH

FIRST Information

EPSS Score: 0.0018

The EPSS (Exploit Prediction Scoring System) is a score from 0 to 1 that indicates the probability that a vulnerability will be exploited in the real world in the next 30 days. A higher value indicates a greater likelihood of exploitation.

Value
0.00.250.50.751.0

Percentile: 0.0787

The Percentile indicates how much higher this vulnerability's EPSS score is compared to all other vulnerabilities in the EPSS database. For example, a percentile of 0.90 (90%) means that 90% of vulnerabilities have an EPSS score equal to or lower than the current one.

Value
0.00.250.50.751.0

*Data updated as of: 2026-09-18


CISA Information (Known Exploited Vulnerabilities)

The CISA KEV Catalog lists vulnerabilities that have been actively exploited in the real world. If a CVE is present in this catalog, it indicates that the threat is immediate and mitigation should be a top priority.

CVE CVE-2026-89930 is not present in the CISA KEV Catalog. This indicates that it is not currently classified by CISA as an actively exploited vulnerability.


Articles published on Red Hot Cyber

No articles present on Red Hot Cyber.


Exploit PoC from GitHub

Connection error to GitHub, or rate limit exceeded. Please try again later.