CVE-2026-74613
Last modified
CVE-2026-74613 is a vulnerability of currently unknown severity. 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..
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= b917507e5ad983085d29069369778b16aa03a0a8, < a7658508f5fe8f1077a65e8cb9535d3426f37a2f; >= b917507e5ad983085d29069369778b16aa03a0a8, < 1aa21e7c8702a7c37cd7d3cace1a652cfa5e8171; >= b917507e5ad983085d29069369778b16aa03a0a8, < 4d37e3525cc346a1421c1bdeaad5848e249fc60c; >= b917507e5ad983085d29069369778b16aa03a0a8, < 9d80a04129a6c27a690cb69de3fe3f50be5aa8b9; >= b917507e5ad983085d29069369778b16aa03a0a8, < a309b74e3fc052352ab778500449cb9c3853c363; >= b917507e5ad983085d29069369778b16aa03a0a8, < 38c7763fdc533edb34dc8f4489c260e8ba2ccae9; >= b917507e5ad983085d29069369778b16aa03a0a8, < e82a5faea2e3886dfb2a65ce092a132e7e896915; >= b917507e5ad983085d29069369778b16aa03a0a8, < a31e0ad444698d8aa7534a0f89fda543730f97a5 |
| Linux | Linux | 5.3 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74613?
How severe is CVE-2026-74613?
How do I fix CVE-2026-74613?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-74608In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74609In the Linux kernel, the following vulnerability has been re…
- CVE-2026-7461Improper neutralization of inputs used in an OS command in t…7.5
- CVE-2026-74610In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74611In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74612In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74614In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74615In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74616In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74617In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74618In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74619In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-74613?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
