Skip to content
Threat Brief

← All advisories

CVE-2026-99578

Severity unknownNo known exploitationFix available

wifi: rtw88: usb: route bmc frames via the high queue only for DTIM delivery

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 10% 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: rtw88: usb: route bmc frames via the high queue only for DTIM delivery In AP mode every broadcast and multicast data frame is routed to TX_DESC_QSEL_HIGH, the after-DTIM queue, whether or not anybody is asleep. The firmware drains that queue at beacon pace, a dozen or so frames per second measured on RTL8822BU, while one associated client's mDNS/SSDP chatter alone exceeds that. The excess accumulates inside the chip until the shared TX page pool is exhausted (measured: 14 of 1803 pages left). From that point every host-sourced frame queues behind the backlog: authentication responses reach the air seconds after the client has given up, so no station can associate anymore, and the beacon reserved-page download fails the BCN_VALID poll ("error beacon valid") because it needs pages from the same pool. The AP keeps beaconing, so the failure looks like a silent RX stall and only a reboot recovers. mac80211 already decides when after-DTIM delivery is needed: it sets IEEE80211_TX_CTL_SEND_AFTER_DTIM on bmc frames only while at least one station is actually dozing. Honor that instead of routing unconditionally: flagged frames keep going through the high queue with the MORE_DATA and HGQMD handling introduced by commit 076f786a0ae1 ("wifi: rtw88: Fix AP mode incorrect DTIM behavior"), everything else leaves at line rate through the AC queues. This partially reverts the usb.c hunk of that commit, whose unconditional routing is what lets the backlog build up. On a bench AP (USB2, 20 MHz, WPA2, hostapd, a Windows client driven through disconnect/reconnect cycles): reconnects fail 0/5 on RTL8822BU and 0/3 on RTL8821CU before this change, and pass 10/10 and 5/5 with it, with the page pool staying healthy and no beacon errors logged.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 8da3a71216a0ecd02980dff5cf9739376249fc728da3a71216a0ecd02980dff5cf9739376249fc72CVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before aa383c35d3e3688da8da0993f751c7b4bab66b02aa383c35d3e3688da8da0993f751c7b4bab66b02CVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 781af5ab5a848b3c0767c0f057bd6692e3b7c17e781af5ab5a848b3c0767c0f057bd6692e3b7c17eCVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before c710c7c2e0380d7c0eeb33b686262edcaef7cb07c710c7c2e0380d7c0eeb33b686262edcaef7cb07CVE Program
LinuxLinuxall versions before 6.12.1186.12.118CVE Program
LinuxLinuxall versions before 6.18.646.18.64CVE Program
LinuxLinuxall versions before 7.3.57.3.5CVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references