Quick answers
- Is CVE-2026-93271 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93271 being exploited in the wild.
- How severe is CVE-2026-93271?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Linux kernel multiple kernel versions with ath11k driver.
- Is there a fix for CVE-2026-93271?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-93271 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-93271?
- Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The ath11k_dp_rx_h_rate() function in drivers/net/wireless/ath/ath11k/dp_rx.c did not validate received HT/VHT/HE frame MCS values against mac80211 limits before processing; frames with out-of-range MCS (e.g. HE MCS 12 when max is 11) left rx_status->rate_idx in an invalid state while encoding remained unset, causing mac80211 to reject them. The fix caps out-of-range MCS values to valid maximums and sets the encoding field correctly, allowing frames to be processed rather than dropped.
Affected products
- Linux kernel multiple kernel versions with ath11k driver
Timeline
- 2026-07-01: other: Initial patch authored
- 2026-09-24: disclosed