wifi: ath12k: fix stride mismatch in mac_phy_caps_parse()
CVE-2026-90399 · 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-90399?
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: d889913205cf7ebda905b1e62c5867ed4e39f6c2 to < 79c6f4f7d16eea1bcb8bc5c8fd6ec04a01b0614f, d889913205cf7ebda905b1e62c5867ed4e39f6c2 to < d3355e0fdbbf531ca8b82a6a3feb80a1b7306a8b, d889913205cf7ebda905b1e62c5867ed4e39f6c2 to < b9a5d12cbdeb860306f8d47c92caee0ea6ee0e0a, d889913205cf7ebda905b1e62c5867ed4e39f6c2 to < 26f8f87f0a556e7984366c64cebc16d49e15d22f
- Linux Linux: 6.3
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: ath12k: fix stride mismatch in mac_phy_caps_parse()
Currently, in ath12k_wmi_mac_phy_caps_parse(), kzalloc() sizes the
mac_phy_caps buffer as tot_phy_id * len, where len is clamped to
min(firmware_len, sizeof(struct ath12k_wmi_mac_phy_caps_params)). 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 ath12k_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.
Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_UPSTREAM-3
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/79c6f4f7d16eea1bcb8bc5c8fd6ec04a01b0614f
- git.kernel.org/stable/c/d3355e0fdbbf531ca8b82a6a3feb80a1b7306a8b
- git.kernel.org/stable/c/b9a5d12cbdeb860306f8d47c92caee0ea6ee0e0a
- git.kernel.org/stable/c/26f8f87f0a556e7984366c64cebc16d49e15d22f
- git.kernel.org/stable/c/4c6eb712a91fa079be6f9f1419c96e0ad2227081
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON