Vulnerability · Published Sep 11, 2026 · Assigned by Linux

CVE-2026-80947wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 94.3% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_list and, once the list grows past RTL8XXXU_RX_URB_PENDING_WATER, schedules rx_urb_wq. The worker rtl8xxxu_rx_urb_work() drains rx_urb_pending_list, recovers priv through container_of, and resubmits each URB through rtl8xxxu_submit_rx_urb(), which anchors it on rx_anchor and dereferences priv->udev. rtl8xxxu_stop() cancels the sibling work items (c2hcmd_work, ra_watchdog, update_beacon_work) but never cancels rx_urb_wq, so a worker armed during the last burst of RX traffic can run rtl8xxxu_rx_urb_work() after rtl8xxxu_disconnect() has called ieee80211_free_hw(), which frees priv, producing a use-after-free. The window opens under active RX traffic (pending count above the watermark) followed by a disconnect. There are two teardown races to close: * rtl8xxxu_queue_rx_urb() decided whether to enqueue under rx_urb_lock but called schedule_work() after dropping the lock. A completion that observed shutdown == false and released the lock could then call schedule_work() after rtl8xxxu_stop() had set shutdown and cancel_work_sync() had already returned, arming the worker to run after the teardown. Move schedule_work() under the same !shutdown branch so the arming decision is atomic with the shutdown check. * rtl8xxxu_rx_urb_work() anchors every URB it drained back onto rx_anchor through rtl8xxxu_submit_rx_urb(). A worker still running when usb_kill_anchored_urbs(&priv->rx_anchor) returned would submit a URB that escaped the kill. In rtl8xxxu_stop(), call cancel_work_sync(&priv->rx_urb_wq) before the kill so the worker is drained first. After priv->shutdown is set under rx_urb_lock, completions can no longer queue rx_urb_wq. cancel_work_sync() then drains the last queued or running worker, and the following usb_kill_anchored_urbs() kills the URBs it may have submitted. rtl8xxxu_disconnect() is covered because ieee80211_unregister_hw() guarantees .stop() runs for a live interface before ieee80211_free_hw() frees priv. The probe error path needs no cancel: rx_urb_wq is INIT_WORK()'d there but cannot have been scheduled, since no URB is submitted before ieee80211_register_hw() succeeds. This bug was found by static analysis.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-80947
Debian:13linux6.12.111-1DEBIAN-CVE-2026-80947
Debian:14linux7.2.6-1DEBIAN-CVE-2026-80947
Debian:12linux-6.126.12.111-1~deb12u1DEBIAN-CVE-2026-80947
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-aws7.0.0-1016.17UBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-gcp7.0.0-1016.18UBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-ibm7.0.0-1017.17UBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1038.42UBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1017.17UBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-oracle7.0.0-1015.16UBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-80947
Ubuntu:26.04:LTSlinux-riscv7.0.0-42.42.1UBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-80947
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-80947
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-80947

Affected products (as reported)

VendorProductVersions
Linux Linux 26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa – before 75e7e19e9218e3b895e652f04acf08113dc3aa0026f1fad29ad973b0fb26a9ca3dcb2a73dde781aa – before da1678cca182567fd84618b689f4424f3f55f71226f1fad29ad973b0fb26a9ca3dcb2a73dde781aa – before 06e6bbb0abc2ae22e6e4d184250075e5c9e090d626f1fad29ad973b0fb26a9ca3dcb2a73dde781aa – before 17d5ae58973122eea7625a87cd3d80a8beb23b4726f1fad29ad973b0fb26a9ca3dcb2a73dde781aa – before 800d2b490a9af1e7132a3564c2ad5a81292e5b4026f1fad29ad973b0fb26a9ca3dcb2a73dde781aa – before 620acb1e8037b73a457dc8ef20fc23fc7adcb40526f1fad29ad973b0fb26a9ca3dcb2a73dde781aa – before 972ab8b9c08f3eb3fa535082de2950dd93604dfd26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa – before 6c080026ecc17eecb103f8927c64ea73a74bb818
Linux Linux 4.4

References