{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93271 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93271 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93271 and fix it if it is affected.\n\nWhat it is: CVE-2026-93271 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93271 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93271/ (Markdown: https://insights.sbomify.com/CVE-2026-93271/index.md)","id":"CVE-2026-93271","markdown":"https://insights.sbomify.com/CVE-2026-93271/index.md","name":"CVE-2026-93271","record":{"aliases":["BELL-CVE-2026-93271","DEBIAN-CVE-2026-93271","GHSA-322g-prc2-r52c","UBUNTU-CVE-2026-93271"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel WiFi driver","requires_auth":"none","summary":"An attacker within WiFi range can cause valid frames to be dropped by triggering a kernel warning via out-of-range MCS values in ath11k driver.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate\n\nath11k can receive HT/VHT/HE frames whose reported MCS is above the\nmaximum that can be expressed in the corresponding mac80211 rate space\n(e.g. an HE frame reported with MCS 12, while HE tops out at MCS 11).\n\nThe frame itself is valid and decodes correctly, but for such a frame\nath11k_dp_rx_h_rate() leaves rx_status-\u003erate_idx set to the out-of-range\nvalue and never assigns rx_status-\u003eencoding, so it stays RX_ENC_LEGACY\nfrom the ath11k_dp_rx_h_ppdu() initialization. Once that frame reaches\nmac80211 it trips the rate sanity check and the frame is dropped with a\nsplat:\n\n  ath11k_pci 0000:03:00.0: Received with invalid mcs in HE mode 12\n  WARNING: CPU: 0 PID: 0 at net/mac80211/rx.c:5433 ieee80211_rx_list+0xb0a/0xe90 [mac80211]\n\nDropping the frame would discard otherwise valid data, so instead cap the\nreported MCS to the maximum the rate space can express and deliver the\nframe. Set rx_status-\u003eencoding before the range check and assign rate_idx\nfrom the capped value, so a frame with an out-of-range MCS no longer\nleaves partial or bogus rate metadata behind. Also downgrade the logging\nlevel since they are not treated as invalid frames now. The only loss is\nthat such a frame is reported as the capped MCS in the rx rate statistics.\n\nTested-on: WCN6855 hw2.1 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate","id":"CVE-2026-93271","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"remoteproc: qcom_wcnss: Fix handling the lack of PD regulators in v3","id":"CVE-2026-93272"},"packages":[],"prev":{"headline":"bpf: Disallow interpreter fallback for BPF_ADDR_PERCPU insn","id":"CVE-2026-93270"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An attacker within WiFi range can cause valid frames to be dropped by triggering a kernel warning via out-of-range MCS values in ath11k driver.","url":"https://insights.sbomify.com/CVE-2026-93271/"}