CVE-2026-89930

CRITICAL CVSS 9.3

Published: 2026-09-16

Modified: 2026-09-16

Enriched via mock

Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-89930 is a moderate vulnerability affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

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.

Attack Chain

Reconnaissance

Attacker scans for vulnerable versions using version banners or PoC scanners

Initial Access

Attacker triggers CVE-2026-89930 vulnerability with a crafted request or payload

Execution

Vulnerability exploited to perform unauthorized actions on the target system

Impact

Depending on vulnerability type, attacker achieves data access, service disruption, or code execution

MITRE ATT&CK Techniques

T1190 Exploit Public-Facing Application

Initial Access

Public-facing application vulnerability exploited for initial access

T1203 Exploitation for Client Execution

Execution

Vulnerability exploited to execute attacker-controlled code

Indicators of Compromise

Type	Value	Description
user_agent	`Mozilla/5.0 (compatible; exploit/1.0)`	Generic exploit scanner user agent pattern
url	`/api/vuln-endpoint?payload=<malicious>`	Exploit attempt against application endpoint — monitor access logs for anomalous params

Remediation

1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.

Quick Facts

CVE ID	CVE-2026-89930
CVSS Score	9.3
Vector	`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`
Published	2026-09-16
Exploited	No
CISA KEV	No
PoC	Not public

References

External Resources

NVD Entry BleepingComputer The Hacker News