Linux kernel Wi-Fi traffic disruption in rtw88 USB after-DTIM queue
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| Linux Linux | — |
|
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 dtim_period 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.
From the CVE record · Linux
The Linux kernel's rtw88 USB driver does not limit frames sent to its after-DTIM queue. When a station is in power-save mode, sustained broadcast or multicast traffic can exhaust the transmit page pool, delaying authentication responses and disrupting the AP until it is rebooted. The input does not specify whether an attacker needs authentication or user interaction.
Operators of Linux access points using the rtw88 USB driver should check their systems; affected versions are not specified.