wifi: mac80211: fix tid_tx use-after-free on BA session stop
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: fix tid_tx use-after-free on BA session stop
ieee80211_stop_tx_ba_cb() hands tid_tx to kfree_rcu() through ieee80211_remove_tid_tx(), and then reads tid_tx->ndp after dropping sta->lock:
ieee80211_remove_tid_tx(sta, tid); /* kfree_rcu(tid_tx, rcu_head) */ ... spin_unlock_bh(&sta->lock);
if (start_txq) ieee80211_agg_start_txq(sta, tid, false);
if (send_delba) ieee80211_send_delba(..., tid_tx->ndp);
That read is not covered by an RCU read-side critical section, and it runs in preemptible process context: both callers hold the wiphy mutex, reaching it either from the ieee80211_ba_session_work() wiphy work or from ieee80211_sta_tear_down_BA_sessions() during station teardown. Softirqs can run in that window too, both from the local_bh_enable() that ends ieee80211_agg_start_txq() and from any interrupt exit, so the RCU callback can free tid_tx before the read.
Driving the function from a test module with the grace period forced into that window, KASAN reports the read, and the free arrives on the ordinary RCU softirq path:
From the CVE record · Linux
The Linux kernel’s mac80211 code can read a freed tid_tx field while stopping a Wi-Fi block acknowledgment (BA) session. The issue occurs during local teardown, including idle timeout, PTK rekey, suspend, or hardware reconfiguration; it is not reached through a peer’s DELBA. The input does not establish an attacker capability, authentication requirement, or required user interaction.
Engineers running Linux kernels with mac80211 should check whether their kernel includes the fix; affected versions were not provided.