Answer in brief
CVE-2026-90398 records a Unknown severity vulnerability in wifi: ath11k: fix stride mismatch in mac_phy_caps_parse(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5b90fc760db5a969ed26d70f8e62c91915f012bd <bbb3b3334a9ed850c5b332eedea107796e691237 || >=5b90fc760db5a969ed26d70f8e62c91915f012bd <75185e2b214e842b7e0af29e5d1fef155662b8b1 || >=5b90fc760db5a969ed26d70f8e62c91915f012bd <acff2713c3212ade15051e7b421f15c89927e70f || >=5b90fc760db5a969ed26d70f8e62c91915f012bd <7a246c72132eb943b5844ba79dad597b47429dba | bbb3b3334a9ed850c5b332eedea107796e691237, 75185e2b214e842b7e0af29e5d1fef155662b8b1, acff2713c3212ade15051e7b421f15c89927e70f, 7a246c72132eb943b5844ba79dad597b47429dba |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.