CVE-2026-90398
CVE CVE-2026-90398EUVD EUVD-2026-82059Published 2026-09-17T16:09:29.000ZLast changed 2026-09-18T17:55:05.000ZCVSS 8.4
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 0; 5b90fc760db5a969ed26d70f8e62c91915f012bd <bbb3b3334a9ed850c5b332eedea107796e691237; patch: 7.3-rc1; patch: 7.2.6; 5.6; 5b90fc760db5a969ed26d70f8e62c91915f012bd <acff2713c3212ade15051e7b421f15c89927e70f; patch: 6.18.52; patch: 6.12.110; 5b90fc760db5a969ed26d70f8e62c91915f012bd <7a246c72132eb943b5844ba79dad597b47429dba; 5b90fc760db5a969ed26d70f8e62c91915f012bd <75185e2b214e842b7e0af29e5d1fef155662b8b1
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.