CVE-2026-99768 in Linux
Summary
by MITRE • 11/20/2026
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: reinstate IEEE80211_TX_CTL_AMPDU flag in ieee80211_tx_prep_agg()
The commit 592234e941f1 ("wifi: mac80211: Fix iTXQ AMPDU fragmentation handling") changed the way handling of the IEEE80211_TX_CTL_AMPDU flag is done in mac80211, so the only place it is set is in ieee80211_tx_dequeue().
This means that any frames that are sent to the driver via drv_tx() will no longer have the flag set. In particular, this affects packets going through ieee80211_tx_pending(). 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 ieee80211_tx_prep_agg() 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability described involves a regression in the Linux kernel's mac80211 wireless subsystem where the IEEE80211_TX_CTL_AMPDU transmission control flag was inadvertently removed from certain frame processing paths due to changes made for iTXQ AMPDU fragmentation handling. This issue stems from commit 592234e941f1 which altered how the ampdu flag is managed within mac80211, restricting its setting exclusively to ieee80211_tx_dequeue(). Consequently frames transmitted via drv_tx(), particularly those processed through ieee80211_tx_pending(), no longer carry this critical indicator. The absence of this flag disrupts driver-level logic that relies on it to track packets within a block acknowledgment window, leading to significant operational failures in specific hardware implementations such as the ath9k wireless adapter drivers.
From a technical perspective the core flaw lies in the misalignment between mac80211's internal state management and driver expectations regarding AMPDU aggregation tracking. The IEEE80211_TX_CTL_AMPDU flag serves as a signal to underlying device drivers that a frame is part of an aggregated transmission sequence requiring specific acknowledgment handling mechanisms like block ack windows. When this flag is absent during the drv_tx() call path, drivers fail to correctly account for these packets within their respective window tracking structures. This oversight causes the driver's internal state machine to become desynchronized with actual network activity resulting in a condition where the block ack window overruns its bounds and ultimately stalls transmission operations effectively causing denial of service conditions for wireless connectivity on affected devices.
The operational impact manifests primarily as complete TX stalling within ath9k drivers which depend heavily on accurate AMPDU flag presence to maintain proper flow control and acknowledgment tracking. Without this synchronization network throughput drops significantly or ceases entirely until the driver resets its state or recovers from the stall condition. This represents a functional regression rather than a traditional security exploit but carries implications for system reliability and availability particularly in environments requiring sustained high-throughput wireless connections. The vulnerability aligns with CWE-841 Improper Enforcement of Behavioral Workflow as it involves incorrect handling of protocol-specific behavioral states leading to unintended operational outcomes.
Mitigation strategies involve applying the kernel patch that reinstates the IEEE80211_TX_CTL_AMPDU flag in ieee80211_tx_prep_agg() when operating within a valid block ack window context. This restoration ensures compatibility with drivers expecting this signal while maintaining safety for existing TXQ paths by confirming harmless behavior across different transmission queues. System administrators should prioritize updating to kernel versions containing this fix and verify driver firmware compatibility if custom modifications exist. Continuous monitoring of wireless stack logs can help detect early signs of AMPDU-related stalls allowing proactive intervention before full connectivity loss occurs ensuring stable operation in production environments relying on mac80211-based wireless interfaces.