CVE-2026-99768: wifi: mac80211: reinstate IEEE80211_TX_CTL_AMPDU flag in ieee80211_tx_prep_agg()
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: reinstate IEEE80211TXCTLAMPDU flag in ieee80211txprepagg()
The commit 592234e941f1 ("wifi: mac80211: Fix iTXQ AMPDU fragmentation handling") changed the way handling of the IEEE80211TXCTLAMPDU flag is done in mac80211, so the only place it is set is in ieee80211txdequeue().
This means that any frames that are sent to the driver via drvtx() will no longer have the flag set. In particular, this affects packets going through ieee80211txpending(). Evan reported that this can result in the ath9k driver failing to account such packets in its block ack window, eventually overrunning the window and stalling TX.
Fix this by reinstating the flag in ieee80211txprepagg() when inside a valid block ack window. This should be harmless for the TXQ path, and will reinstate the previous behaviour for drivers that use the flag as a signal to track the packet in the window.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.2 - 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 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1 - Compensating control
Reinstate the IEEE80211_TX_CTL_AMPDU flag in ieee80211_tx_prep_agg().
Event History
Frequently Asked Questions
Which systems are most likely to experience this issue?
Linux systems using mac80211 with drivers that rely on IEEE80211_TX_CTL_AMPDU to track packets in a block-ack window are affected. The reported impact specifically involves the ath9k Wi-Fi driver.
What conditions lead to the transmission stall?
The issue affects frames sent to a driver through drv_tx(), particularly packets processed through ieee80211_tx_pending(). If the driver does not account for those AMPDU packets in its block-ack window, the window can eventually overrun and TX can stall.
How can administrators tell whether they are affected?
A relevant symptom is stalled Wi-Fi transmission on an affected mac80211 system, particularly when using ath9k. The issue is associated with packets handled through ieee80211_tx_pending() that are not tracked in the driver's block-ack window.
What is the available remediation?
Apply a Linux kernel update containing the fix that restores IEEE80211_TX_CTL_AMPDU in ieee80211_tx_prep_agg() for packets within a valid block-ack window. The supplied references identify stable kernel commits containing the correction.