CVE-2026-93271wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate ath11k can receive HT/VHT/HE frames whose reported MCS is above the maximum that can be expressed in the corresponding mac80211 rate space (e.g. an HE frame reported with MCS 12, while HE tops out at MCS 11). The frame itself is valid and decodes correctly, but for such a frame ath11k_dp_rx_h_rate() leaves rx_status->rate_idx set to the out-of-range value and never assigns rx_status->encoding, so it stays RX_ENC_LEGACY from the ath11k_dp_rx_h_ppdu() initialization. Once that frame reaches mac80211 it trips the rate sanity check and the frame is dropped with a splat: ath11k_pci 0000:03:00.0: Received with invalid mcs in HE mode 12 WARNING: CPU: 0 PID: 0 at net/mac80211/rx.c:5433 ieee80211_rx_list+0xb0a/0xe90 [mac80211] Dropping the frame would discard otherwise valid data, so instead cap the reported MCS to the maximum the rate space can express and deliver the frame. Set rx_status->encoding before the range check and assign rate_idx from the capped value, so a frame with an out-of-range MCS no longer leaves partial or bogus rate metadata behind. Also downgrade the logging level since they are not treated as invalid frames now. The only loss is that such a frame is reported as the capped MCS in the rx rate statistics. Tested-on: WCN6855 hw2.1 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 24, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from d5c65159f2895379e11ca13f62feabe93278985d before 6ad04c3e2ec54bf5ec72c81afdd66318a116c539; from d5c65159f2895379e11ca13f62feabe93278985d before a6b951f79e66fc8bd93a537ff1040fbfb567c8bf; from d5c65159f2895379e11ca13f62feabe93278985d before b77bfe6e59b98dff3ccfcf9b45fc27e3db498626; from d5c65159f2895379e11ca13f62feabe93278985d before fb7b9a7209f839c17c66484dfdc84c9a23c6fd2f; from d5c65159f2895379e11ca13f62feabe93278985d before a0b3e6f9645d88f387c4fea546048a91952cd4cd; from d5c65159f2895379e11ca13f62feabe93278985d before 2bb2a778a487305bd378db5fd5014fbdce4ada2c; from d5c65159f2895379e11ca13f62feabe93278985d before ccbd20f2168f581d90265da1a925b9b6472a0b05; from d5c65159f2895379e11ca13f62feabe93278985d before 12b09e478aa7459b7893a695ef77682202f2da83 | CNA record |
References
- https://git.kernel.org/stable/c/6ad04c3e2ec54bf5ec72c81afdd66318a116c539
- https://git.kernel.org/stable/c/a6b951f79e66fc8bd93a537ff1040fbfb567c8bf
- https://git.kernel.org/stable/c/b77bfe6e59b98dff3ccfcf9b45fc27e3db498626
- https://git.kernel.org/stable/c/fb7b9a7209f839c17c66484dfdc84c9a23c6fd2f
- https://git.kernel.org/stable/c/a0b3e6f9645d88f387c4fea546048a91952cd4cd
- https://git.kernel.org/stable/c/2bb2a778a487305bd378db5fd5014fbdce4ada2c
- https://git.kernel.org/stable/c/ccbd20f2168f581d90265da1a925b9b6472a0b05
- https://git.kernel.org/stable/c/12b09e478aa7459b7893a695ef77682202f2da83
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.