CVE-2026-74613

CVE CVE-2026-74613EUVD EUVD-2026-64550Published 2026-08-22T15:31:59.000ZLast changed 2026-08-25T05:40:39.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux b917507e5ad983085d29069369778b16aa03a0a8 <9d80a04129a6c27a690cb69de3fe3f50be5aa8b9; patch: 6.1.183; b917507e5ad983085d29069369778b16aa03a0a8 <a309b74e3fc052352ab778500449cb9c3853c363; patch: 7.2; 5.3; patch: 5.10.265; patch: 5.15.216; b917507e5ad983085d29069369778b16aa03a0a8 <4d37e3525cc346a1421c1bdeaad5848e249fc60c; b917507e5ad983085d29069369778b16aa03a0a8 <38c7763fdc533edb34dc8f4489c260e8ba2ccae9; patch: 6.18.45; patch: 7.1.9; patch: 6.12.104; b917507e5ad983085d29069369778b16aa03a0a8 <a31e0ad444698d8aa7534a0f89fda543730f97a5; b917507e5ad983085d29069369778b16aa03a0a8 <1aa21e7c8702a7c37cd7d3cace1a652cfa5e8171; b917507e5ad983085d29069369778b16aa03a0a8 <e82a5faea2e3886dfb2a65ce092a132e7e896915; patch: 0; b917507e5ad983085d29069369778b16aa03a0a8 <a7658508f5fe8f1077a65e8cb9535d3426f37a2f; patch: 6.6.152

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.