CVE-2026-99577: wifi: rtw88: usb: bound what the driver feeds the after-DTIM queue
In the Linux kernel, the following vulnerability has been resolved:
wifi: rtw88: usb: bound what the driver feeds the after-DTIM queue
Frames routed to the high queue are transmitted right after DTIM beacons only, inside the ATIM window, while they wait in the shared TX page pool. The driver puts no limit on how many it hands over, so as long as one station dozes, any sustained broadcast or multicast traffic outruns the drain and empties the pool: measured on an RTL8822BU AP with a single client in power save and ~40 frames/s of mDNS chatter, the free page count at 0x240 goes from 1803 to 16 in about 100 seconds and stays there for as long as the traffic lasts. From that point every other transmit queues behind the backlog, authentication responses arrive too late for anyone to join, and the reserved page download fails ("error beacon valid"). The AP keeps beaconing and only a reboot recovers.
Feed the high queue through a small budget that refills below the measured drain rate (about 3 frames per DTIM, ~15/s at dtimperiod 2 on the default 2 TU ATIM window); whatever exceeds the budget leaves on its access category queue right away. The high queue backlog is now bounded by the burst size under any load, so the page pool cannot run dry, at the price that a dozing station may miss part of a broadcast storm.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5
Frequently Asked Questions
Which deployments are exposed to this condition?
Access-point use of the rtw88 USB driver is exposed when at least one associated station enters power-save mode and broadcast or multicast traffic is sustained. The described reproduction used an RTL8822BU AP with one power-saving client and mDNS traffic.
What traffic conditions trigger the failure?
Traffic routed to the high queue is held until after DTIM beacons during the ATIM window. Sustained broadcast or multicast traffic can exceed the queue's drain rate while a station is dozing, exhausting the shared transmit page pool.
What is the operational impact and how can it be identified?
Other transmit traffic queues behind the backlog, authentication responses can arrive too late for new clients to join, and reserved-page downloads can fail with "error beacon valid." The AP may continue beaconing despite being unable to reliably serve clients; the reported free-page count dropped from 1803 to 16 and remained low under continued traffic.
What can be done if the AP has already entered this state?
In the reported condition, a reboot was required to recover. The resolution bounds the after-DTIM high-queue input with a small per-DTIM budget, allowing excess traffic to use its access-category queue immediately instead of consuming the shared page pool.