Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 25 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected d5c65159f2895379e11ca13f62feabe93278985d – < 6ad04c3e2ec54bf5ec72c81afdd66318a116c539
    • affected d5c65159f2895379e11ca13f62feabe93278985d – < a6b951f79e66fc8bd93a537ff1040fbfb567c8bf
    • affected d5c65159f2895379e11ca13f62feabe93278985d – < b77bfe6e59b98dff3ccfcf9b45fc27e3db498626
    • affected d5c65159f2895379e11ca13f62feabe93278985d – < fb7b9a7209f839c17c66484dfdc84c9a23c6fd2f
    • affected d5c65159f2895379e11ca13f62feabe93278985d – < a0b3e6f9645d88f387c4fea546048a91952cd4cd
    • affected d5c65159f2895379e11ca13f62feabe93278985d – < 2bb2a778a487305bd378db5fd5014fbdce4ada2c
    • affected d5c65159f2895379e11ca13f62feabe93278985d – < ccbd20f2168f581d90265da1a925b9b6472a0b05
    • affected d5c65159f2895379e11ca13f62feabe93278985d – < 12b09e478aa7459b7893a695ef77682202f2da83
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93271 badge
[![CVE-2026-93271](https://cveledger.app/badge/CVE-2026-93271.svg)](https://cveledger.app/cve/CVE-2026-93271)

Record last updated .