Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-93271: wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 12b09e478aa7459b7893a695ef77682202f2da83, 2bb2a778a487305bd378db5fd5014fbdce4ada2c, 6ad04c3e2ec54bf5ec72c81afdd66318a116c539; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 12b09e478aa7459b7893a695ef77682202f2da83, 2bb2a778a487305bd378db5fd5014fbdce4ada2c, 6ad04c3e2ec54bf5ec72c81afdd66318a116c539; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

—No exploit Fix available
Published
Sep 24, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-93271

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.6affected
    • d5c65159f2895379e11ca13f62feabe93278985d and later · before 6ad04c3e2ec54bf5ec72c81afdd66318a116c539affected · git
    • d5c65159f2895379e11ca13f62feabe93278985d and later · before a6b951f79e66fc8bd93a537ff1040fbfb567c8bfaffected · git
    • d5c65159f2895379e11ca13f62feabe93278985d and later · before b77bfe6e59b98dff3ccfcf9b45fc27e3db498626affected · git
    • d5c65159f2895379e11ca13f62feabe93278985d and later · before fb7b9a7209f839c17c66484dfdc84c9a23c6fd2faffected · git
    • d5c65159f2895379e11ca13f62feabe93278985d and later · before a0b3e6f9645d88f387c4fea546048a91952cd4cdaffected · git
    • d5c65159f2895379e11ca13f62feabe93278985d and later · before 2bb2a778a487305bd378db5fd5014fbdce4ada2caffected · git
    • d5c65159f2895379e11ca13f62feabe93278985d and later · before ccbd20f2168f581d90265da1a925b9b6472a0b05affected · git
    • d5c65159f2895379e11ca13f62feabe93278985d and later · before 12b09e478aa7459b7893a695ef77682202f2da83affected · git
    • before 5.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93269Sep 24, 2026 · ext4: fix circular lock dependency in ext4_ext_migrate
    0Monitor
  • ← EarlierCVE-2026-93270Sep 24, 2026 · bpf: Disallow interpreter fallback for BPF_ADDR_PERCPU insn
    0Monitor
  • Later →CVE-2026-93272Sep 24, 2026 · remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux12b09e478aa7459b7893a695ef77682202f2da83Vendor (CNA)
Linux Linux2bb2a778a487305bd378db5fd5014fbdce4ada2cVendor (CNA)
Linux Linux6ad04c3e2ec54bf5ec72c81afdd66318a116c539Vendor (CNA)
Linux Linuxa0b3e6f9645d88f387c4fea546048a91952cd4cdVendor (CNA)
Linux Linuxa6b951f79e66fc8bd93a537ff1040fbfb567c8bfVendor (CNA)
Linux Linuxb77bfe6e59b98dff3ccfcf9b45fc27e3db498626Vendor (CNA)
Linux Linuxccbd20f2168f581d90265da1a925b9b6472a0b05Vendor (CNA)
Linux Linuxfb7b9a7209f839c17c66484dfdc84c9a23c6fd2fVendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records