---
title: "CVE-2026-80932: Linux Kernel virtio_vsock - Use After Free"
description: "Linux kernel virtio_vsock contains a use-after-free vulnerability caused by improper flushing order of dependent work items in virtio_vsock_remove(), letting attackers cause memory corruption or system instability, exploit requires kernel-level access."
url: https://panop.io/threat-heartbeat/CVE-2026-80932/
---

# CVE-2026-80932 Linux Kernel virtio\_vsock - Use After Free

Linux kernel virtio\_vsock contains a use-after-free vulnerability caused by improper flushing order of dependent work items in virtio\_vsock\_remove(), letting attackers cause memory corruption or system instability, exploit requires kernel-level access.

CVSS base score 8.4 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.14% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-80932)

## Details

Type

Use After Free

Impact

Denial Of Service, Privilege Escalation

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Published

11 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix for virtio\_vsock work flush order.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-80932](https://nvd.nist.gov/vuln/detail/CVE-2026-80932)
- [https://git.kernel.org/stable/c/531e2ac2dab1ab90a16427c4f9c86663633e9487](https://git.kernel.org/stable/c/531e2ac2dab1ab90a16427c4f9c86663633e9487)
- [https://git.kernel.org/stable/c/b9cb4e8ba71c9fbd935d66baa71bbb0b87192c94](https://git.kernel.org/stable/c/b9cb4e8ba71c9fbd935d66baa71bbb0b87192c94)
- [https://git.kernel.org/stable/c/e059a14c1067bcc4f7b1947cd09f2baab98e340f](https://git.kernel.org/stable/c/e059a14c1067bcc4f7b1947cd09f2baab98e340f)
- [https://git.kernel.org/stable/c/f3313d952fc380cff53db9a28451a8807aa67b43](https://git.kernel.org/stable/c/f3313d952fc380cff53db9a28451a8807aa67b43)
- [https://git.kernel.org/stable/c/165a330a68b5f299d8735f0194c314cb2e571269](https://git.kernel.org/stable/c/165a330a68b5f299d8735f0194c314cb2e571269)
- [https://git.kernel.org/stable/c/2187a56f2fd1715d54daed6392809223c60544f3](https://git.kernel.org/stable/c/2187a56f2fd1715d54daed6392809223c60544f3)
- [https://git.kernel.org/stable/c/728836ebca239810f164262b10211ef59182f811](https://git.kernel.org/stable/c/728836ebca239810f164262b10211ef59182f811)
- [https://git.kernel.org/stable/c/da5e9f08714c19ba04e6863aca69d40f042f2e04](https://git.kernel.org/stable/c/da5e9f08714c19ba04e6863aca69d40f042f2e04)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)