CVE-2026-74613

vsock/virtio: avoid refilling the RX queue after teardown

State
Published
Severity
7.8 High
Published
Aug 22, 2026
Updated
Oct 16, 2026
Reserved
Aug 15, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • b917507e5ad983085d29069369778b16aa03a0a8 to before a7658508f5fe8f1077a65e8cb9535d3426f37a2fAffected
  • b917507e5ad983085d29069369778b16aa03a0a8 to before 1aa21e7c8702a7c37cd7d3cace1a652cfa5e8171Affected
  • b917507e5ad983085d29069369778b16aa03a0a8 to before 4d37e3525cc346a1421c1bdeaad5848e249fc60cAffected
  • b917507e5ad983085d29069369778b16aa03a0a8 to before 9d80a04129a6c27a690cb69de3fe3f50be5aa8b9Affected
  • b917507e5ad983085d29069369778b16aa03a0a8 to before a309b74e3fc052352ab778500449cb9c3853c363Affected
  • b917507e5ad983085d29069369778b16aa03a0a8 to before 38c7763fdc533edb34dc8f4489c260e8ba2ccae9Affected
  • b917507e5ad983085d29069369778b16aa03a0a8 to before e82a5faea2e3886dfb2a65ce092a132e7e896915Affected
  • b917507e5ad983085d29069369778b16aa03a0a8 to before a31e0ad444698d8aa7534a0f89fda543730f97a5Affected
LinuxLinux
  • 5.3Affected
  • before 5.3Not affected
  • 5.10.265 through 5.10.*Not affected
  • 5.15.216 through 5.15.*Not affected
  • 6.1.183 through 6.1.*Not affected
  • 6.6.152 through 6.6.*Not affected
  • 6.12.104 through 6.12.*Not affected
  • 6.18.45 through 6.18.*Not affected
  • 7.1.9 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.