wifi: ath11k: fix stride mismatch in mac_phy_caps_parse()
CVE-2026-90398 · published 17 Sept 2026
How serious is it
- Severity: high, CVSS score 8.4 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-90398?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 5b90fc760db5a969ed26d70f8e62c91915f012bd to < b2ecd548f89a4a6c14b5eb4abc825f92b3068dda, 5b90fc760db5a969ed26d70f8e62c91915f012bd to < bbb3b3334a9ed850c5b332eedea107796e691237, 5b90fc760db5a969ed26d70f8e62c91915f012bd to < 75185e2b214e842b7e0af29e5d1fef155662b8b1, 5b90fc760db5a969ed26d70f8e62c91915f012bd to < acff2713c3212ade15051e7b421f15c89927e70f
- Linux Linux: 5.6
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: fix stride mismatch in mac_phy_caps_parse()
Currently, in ath11k_wmi_tlv_mac_phy_caps_parse(), kcalloc() sizes the
mac_phy_caps buffer as tot_phy_id * len, where len is clamped to
min(firmware_len, sizeof(struct wmi_mac_phy_capabilities)). The subsequent
memcpy() destination advances by sizeof(full struct) per slot via C
pointer arithmetic, not by the clamped len. When firmware sends short
TLVs, the second and later slots are written past the end of the
allocation.
The reader in ath11k_pull_mac_phy_cap_svc_ready_ext() also indexes the
buffer with full-struct pointer arithmetic, so the allocation must match
that stride.
Fix by using kzalloc_objs(), which derives the element size from the
pointer type, making allocation size and pointer stride provably
consistent regardless of what len the firmware provides.
Compile tested only.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/b2ecd548f89a4a6c14b5eb4abc825f92b3068dda
- git.kernel.org/stable/c/bbb3b3334a9ed850c5b332eedea107796e691237
- git.kernel.org/stable/c/75185e2b214e842b7e0af29e5d1fef155662b8b1
- git.kernel.org/stable/c/acff2713c3212ade15051e7b421f15c89927e70f
- git.kernel.org/stable/c/7a246c72132eb943b5844ba79dad597b47429dba
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON