CVE-2026-93271 — wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate
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
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ d5c65159f2895379e11ca13f62feabe93278985d and < 6ad04c3e2ec54bf5ec72c81afdd66318a116c539≥ d5c65159f2895379e11ca13f62feabe93278985d and < a6b951f79e66fc8bd93a537ff1040fbfb567c8bf≥ d5c65159f2895379e11ca13f62feabe93278985d and < b77bfe6e59b98dff3ccfcf9b45fc27e3db498626≥ d5c65159f2895379e11ca13f62feabe93278985d and < fb7b9a7209f839c17c66484dfdc84c9a23c6fd2f≥ d5c65159f2895379e11ca13f62feabe93278985d and < a0b3e6f9645d88f387c4fea546048a91952cd4cd≥ d5c65159f2895379e11ca13f62feabe93278985d and < 2bb2a778a487305bd378db5fd5014fbdce4ada2c≥ d5c65159f2895379e11ca13f62feabe93278985d and < ccbd20f2168f581d90265da1a925b9b6472a0b05≥ d5c65159f2895379e11ca13f62feabe93278985d and < 12b09e478aa7459b7893a695ef77682202f2da83 and 1 moreversion 5.6 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.20%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/6ad04c3e2ec54bf5ec72c81afdd66318a116c539
- git.kernel.org/stable/c/a0b3e6f9645d88f387c4fea546048a91952cd4cd
- git.kernel.org/stable/c/ccbd20f2168f581d90265da1a925b9b6472a0b05
- git.kernel.org/stable/c/12b09e478aa7459b7893a695ef77682202f2da83
- git.kernel.org/stable/c/fb7b9a7209f839c17c66484dfdc84c9a23c6fd2f
- git.kernel.org/stable/c/2bb2a778a487305bd378db5fd5014fbdce4ada2c
- git.kernel.org/stable/c/b77bfe6e59b98dff3ccfcf9b45fc27e3db498626
- git.kernel.org/stable/c/a6b951f79e66fc8bd93a537ff1040fbfb567c8bf
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 2d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 2d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 3d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 3d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 3d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-93271 is "wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.