CVE-2026-99301 · Package
NO FIX YET
A race in the Linux kernel's virtio-net driver lets queued receive-mode work run after the device's virtqueues were freed during probe unwind or teardown. The sources describe a use-after-free, which can crash the kernel or be abused for memory corruption.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Virtual machines and hosts that use the virtio-net paravirtualized network driver, typically on KVM or other hypervisors, are the exposed systems. The flaw sits in driver probe and teardown paths, so systems without virtio-net devices can skip it. The sources do not state which kernel versions are affected or fixed.
Not affected if no-virtio-net-devices
Who cares kvm, linux-kernel, virtio-net, virtual-machines
uname -r and compare it to the fixed versions in the Linux kernel stable branches.lsmod | grep virtio_net on virtual machines.Unknown from the sources.
In the Linux kernel, the following vulnerability has been resolved:
virtio_net: atomically disable rx mode work
virtio-net uses a boolean to gate rx_mode_work during device teardown. The flag is changed under RTNL, but ndo_set_rx_mode checks it under the address-list lock. A callback can therefore pass the check and enqueue work after teardown has flushed it. The work is also enabled before late probe operations that can fail, allowing probe unwind to free the netdev with work still queued.
KASAN reports the worker using a virtqueue that probe unwind already freed:
BUG: KASAN: slab-use-after-free in virtqueue_add_split Workqueue: events virtnet_rx_mode_work Call Trace: virtqueue_add_split (drivers/virtio/virtio_ring.c:706) virtqueue_add_sgs (drivers/virtio/virtio_ring.c:2839) virtnet_send_command_reply (drivers/net/virtio_net.c:3565) virtnet_rx_mode_work (drivers/net/virtio_net.c:3833) process_one_work (kernel/workqueue.c:3322) worker_thread (kernel/workqueue.c:3405) Freed by task 119: kfree (mm/slub.c:6625) vp_del_vq.isra.0 (drivers/virtio/virtio_pci_common.c:259) vp_del_vqs (drivers/virtio/virtio_pci_common.c:285) virtnet_probe (drivers/net/virtio_net.c:7129)
Use the workqueue disable mechanism to atomically reject new queue attempts and drain running work. Keep work disabled until probe succeeds or restore has reattached the netdev, then enable it and replay receive-mode state for a running interface. Disable it before resource teardown in freeze and remove.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.