---
id: "CVE-2026-99301"
page: "https://infrastack.ai/live/CVE-2026-99301"
kind: "vulnerability"
aliases: ["CVE-2026-99301"]
title: "Linux kernel: virtio-net rx-mode work can use freed virtqueue memory"
severity: "unknown"
cvss: null
epss: 0.00209
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["kvm", "linux-kernel", "package", "virtio-net", "virtual-machines"]
not_affected_if: ["no-virtio-net-devices"]
published_at: "2026-11-16T10:17:03+00:00"
first_seen_at: "2026-11-16T10:39:26+00:00"
updated_at: "2026-11-16T18:53:18+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99301", "first_seen_at": "2026-11-16T10:39:26+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99301", "first_seen_at": "2026-11-16T18:53:18+00:00"}]
exploit_sources: [{"type": "epss", "score": 0.00209, "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99301"}]
---

# Linux kernel: virtio-net rx-mode work can use freed virtqueue memory

Link for people: https://infrastack.ai/live/CVE-2026-99301 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the running kernel version with `uname -r` and compare it to the fixed versions in the Linux kernel stable branches.
- Confirm the virtio_net driver is in use with `lsmod | grep virtio_net` on virtual machines.

## Timeline

- 2026-11-16T10:39:26+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99301
- 2026-11-16T18:53:18+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-99301

## 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
