CVE-2026-93271: Linux kernel · wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fb7b9a7209f839c17c66484dfdc84c9a23c6fd2f : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fb7b9a7209f839c17c66484dfdc84c9a23c6fd2f, ccbd20f2168f581d90265da1a925b9b6472a0b05, b77bfe6e59b98dff3ccfcf9b45fc27e3db498626 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel in the specified commits. Users should update to a Linux kernel version including these fixes to prevent frame drops caused by out-of-range MCS values in ath11k. No additional action is required beyond applying the official fix.
Description
A vulnerability in the Linux kernel's ath11k wireless driver caused frames with out-of-range MCS values to be dropped due to invalid rate metadata. This was fixed by capping the MCS value to the maximum supported and properly setting encoding metadata, allowing valid frames to be processed instead of discarded.
References
- git.kernel.org/stable/c/6ad04c3e2ec54bf5ec72c81afdd66318a116c539 (opens in a new tab)
- git.kernel.org/stable/c/a6b951f79e66fc8bd93a537ff1040fbfb567c8bf (opens in a new tab)
- git.kernel.org/stable/c/b77bfe6e59b98dff3ccfcf9b45fc27e3db498626 (opens in a new tab)
- git.kernel.org/stable/c/fb7b9a7209f839c17c66484dfdc84c9a23c6fd2f (opens in a new tab)
- git.kernel.org/stable/c/a0b3e6f9645d88f387c4fea546048a91952cd4cd (opens in a new tab)
- git.kernel.org/stable/c/2bb2a778a487305bd378db5fd5014fbdce4ada2c (opens in a new tab)
- git.kernel.org/stable/c/ccbd20f2168f581d90265da1a925b9b6472a0b05 (opens in a new tab)
- git.kernel.org/stable/c/12b09e478aa7459b7893a695ef77682202f2da83 (opens in a new tab)