Skip to main content
VulnerabilityPublished Updated

CVE-2026-90398: Linux kernel · wifi: ath11k: fix stride mismatch in mac_phy_caps_parse()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High · fixed in bbb3b3334a9ed850c5b332eedea107796e691237 : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in bbb3b3334a9ed850c5b332eedea107796e691237, b2ecd548f89a4a6c14b5eb4abc825f92b3068dda, acff2713c3212ade15051e7b421f15c89927e70f +2
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 5b90fc760db5a969ed26d70f8e62c91915f012bd, < bbb3b3334a9ed850c5b332eedea107796e691237
Fixed in
  • bbb3b3334a9ed850c5b332eedea107796e691237
LinuxLinuxAffected
  • ≥ 5b90fc760db5a969ed26d70f8e62c91915f012bd, < b2ecd548f89a4a6c14b5eb4abc825f92b3068dda
Fixed in
  • b2ecd548f89a4a6c14b5eb4abc825f92b3068dda
LinuxLinuxAffected
  • ≥ 5b90fc760db5a969ed26d70f8e62c91915f012bd, < acff2713c3212ade15051e7b421f15c89927e70f
Fixed in
  • acff2713c3212ade15051e7b421f15c89927e70f
LinuxLinuxAffected
  • ≥ 5b90fc760db5a969ed26d70f8e62c91915f012bd, < 75185e2b214e842b7e0af29e5d1fef155662b8b1
Fixed in
  • 75185e2b214e842b7e0af29e5d1fef155662b8b1
LinuxLinuxAffected
  • ≥ 5b90fc760db5a969ed26d70f8e62c91915f012bd, < 7a246c72132eb943b5844ba79dad597b47429dba
Fixed in
  • 7a246c72132eb943b5844ba79dad597b47429dba
LinuxLinuxAffected
  • =5.6
Fixed in–

Description

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.

References

Community reviews

Loading reviews…