CVE-2026-64115
Linux kernel vsock/VMCI UAF can crash host or allow guest->host escalation.
Is CVE-2026-64115 being exploited?
Not confirmed. CVE-2026-64115 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-64115?
CVE-2026-64115 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64115?
Yes. A fix has been recorded for CVE-2026-64115. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64115 affect?
CVE-2026-64115 affects Linux kernel (vsock/vmci), Virtualized hosts and guests using VMCI/vsock. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64115?
Apply kernel updates, reboot affected hosts/VMs, disable VMCI if not required.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free in vsock/VMCI causes kernel memory corruption, enabling host crashes or potential guest-to-host privilege escalation.
Immediate action required
- affected>= d021c344051af91f42c5ba9fdedc176740cbd238 and < 1e19f08552b90070ed18bafb1763c78297823af6
- affected>= d021c344051af91f42c5ba9fdedc176740cbd238 and < 1dd531e28f61edd286edc486ab068f135b5ae1eb
- affected>= d021c344051af91f42c5ba9fdedc176740cbd238 and < ecda37f8faab3220da199335e42564cb7a9ad145
- affected>= d021c344051af91f42c5ba9fdedc176740cbd238 and < cc27e989a5dfdfcfc1cca7c3be27a0c7532b46cb
- affected>= d021c344051af91f42c5ba9fdedc176740cbd238 and < 47e63077605c6c2aa45b3df9847a8cdc1f1f6ef9
- affected>= d021c344051af91f42c5ba9fdedc176740cbd238 and < 440447699c681e26ed58e9c309cad718270a18b4
- affected>= d021c344051af91f42c5ba9fdedc176740cbd238 and < 9fe74e42914c851d68069713b7b917a9c33faf26
- affected>= d021c344051af91f42c5ba9fdedc176740cbd238 and < 99e22ddf4edb63dc8382bc028af928056d3450cf
- affected3.9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.