Skip to content
major vulnerability· requires attention

Kernel-level use-after-free in virtio_vsock can enable host/guest kernel compromise; affects widely deployed virtualization stacks and could disrupt infrastructure.

Systems

CVE-2026-80932

8.4
High
EPSS 0.14%Patch availableSep 14, 2026

Linux kernel virtio_vsock use-after-free enabling potential kernel RCE

common questions

Is CVE-2026-80932 being exploited?

Not confirmed. CVE-2026-80932 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-80932?

CVE-2026-80932 is rated High with a CVSS score of 8.4. 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-80932?

Yes. A fix has been recorded for CVE-2026-80932. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-80932 affect?

CVE-2026-80932 affects Linux kernel (virtio_vsock), KVM/QEMU hypervisors, Virtual machines using virtio-vsock. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-80932?

Apply updated kernel/release from vendor and reboot hosts/VMs; isolate untrusted VMs until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (virtio_vsock)KVM/QEMU hypervisorsVirtual machines using virtio-vsock
impact

Use-after-free in virtio_vsock workqueue can cause kernel memory corruption, crashes or remote code execution via crafted virtio queues (guest↔host).

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and < 2187a56f2fd1715d54daed6392809223c60544f3
  • affected>= 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and < 165a330a68b5f299d8735f0194c314cb2e571269
  • affected>= 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and < da5e9f08714c19ba04e6863aca69d40f042f2e04
  • affected>= 0ea9e1d3a9e3ef7d2a1462d3de6b95131dc7d872 and < 728836ebca239810f164262b10211ef59182f811
  • affected4.8
vendor says fixed in< 4.8, >= 6.12.109 and <= 6.12.*, >= 6.18.50 and <= 6.18.*, >= 7.2.4 and <= 7.2.*, >= 7.3-rc1 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free