Skip to content
Threat Brief

← All advisories

CVE-2026-80947

High 7.8No known exploitationFix available

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

Record last updated

CVSS score

7.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa before 800d2b490a9af1e7132a3564c2ad5a81292e5b40800d2b490a9af1e7132a3564c2ad5a81292e5b40CVE Program
LinuxLinuxfrom 26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa before 620acb1e8037b73a457dc8ef20fc23fc7adcb405620acb1e8037b73a457dc8ef20fc23fc7adcb405CVE Program
LinuxLinuxfrom 26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa before 6c080026ecc17eecb103f8927c64ea73a74bb8186c080026ecc17eecb103f8927c64ea73a74bb818CVE Program
LinuxLinuxfrom 26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa before 972ab8b9c08f3eb3fa535082de2950dd93604dfd972ab8b9c08f3eb3fa535082de2950dd93604dfdCVE Program
LinuxLinuxfrom 26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa before 75e7e19e9218e3b895e652f04acf08113dc3aa0075e7e19e9218e3b895e652f04acf08113dc3aa00CVE Program
LinuxLinuxfrom 26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa before da1678cca182567fd84618b689f4424f3f55f712da1678cca182567fd84618b689f4424f3f55f712CVE Program
LinuxLinuxfrom 26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa before 06e6bbb0abc2ae22e6e4d184250075e5c9e090d606e6bbb0abc2ae22e6e4d184250075e5c9e090d6CVE Program
LinuxLinuxfrom 26f1fad29ad973b0fb26a9ca3dcb2a73dde781aa before 17d5ae58973122eea7625a87cd3d80a8beb23b4717d5ae58973122eea7625a87cd3d80a8beb23b47CVE Program
LinuxLinux4.4Not documentedCVE Program
Microsoftazl3 kernel 6.6.150.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.152.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.157.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 kernel 6.6.159.1-1 on Azure Linux 3.0Not documented6.6.161.1-1Microsoft MSRC
LinuxLinux (unaffected)from 5.10.273 up to and including 5.10.*Not documentedCVE Program
LinuxLinux (unaffected)from 5.15.224 up to and including 5.15.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.1.191 up to and including 6.1.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.109 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.50 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.160 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.4 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.4Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Advisory change

    Microsoft advisory revised (6.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  8. Advisory change

    Microsoft advisory revised (7.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  9. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references