cbcvebase.
CVE-2026-64037
published 2026-07-19

CVE-2026-64037: In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mld: fix TSO segmentation explosion when AMSDU is disabled When the TLC…

PriorityP350critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.43%
35.5th percentile
In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mld: fix TSO segmentation explosion when AMSDU is disabled When the TLC notification disables AMSDU for a TID, the MLD driver sets max_tid_amsdu_len to the sentinel value 1. The TSO segmentation path in iwl_mld_tx_tso_segment() checks for zero but not for this sentinel, allowing it to reach the num_subframes calculation: num_subframes = (max_tid_amsdu_len + pad) / (subf_len + pad) = (1 + 2) / (1534 + 2) = 0 This zero propagates to iwl_tx_tso_segment() which sets: gso_size = num_subframes * mss = 0 Calling skb_gso_segment() with gso_size=0 creates over 32000 tiny segments from a single GSO skb. This floods the TX ring with ~1024 micro-frames (the rest are purged), creating a massive burst of TX completion events that can lead to memory corruption and a subsequent use-after-free in TCP's retransmit queue (refcount underflow in tcp_shifted_skb, NULL deref in tcp_rack_detect_loss). The MVM driver is immune because it checks mvmsta->amsdu_enabled before reaching the num_subframes calculation. The MLD driver has no equivalent bitmap check and relies solely on max_tid_amsdu_len, which does not catch the sentinel value. Fix this by detecting the sentinel value (max_tid_amsdu_len == 1) at the existing check and falling back to non-AMSDU TSO segmentation. Also add a WARN_ON_ONCE guard after the num_subframes division as defense-in-depth to catch any future code paths that produce zero through a different mechanism.

Affected

23 ranges
VendorProductVersion rangeFixed in
linuxlinux——
linuxlinux>= d1e879ec600f9b3bdd253167533959facfefb17b < 9e360e610a73f62432e986775023d5382773f0459e360e610a73f62432e986775023d5382773f045
linuxlinux>= d1e879ec600f9b3bdd253167533959facfefb17b < cbe1c8245e4469d1aa6e12e5d913611376d23788cbe1c8245e4469d1aa6e12e5d913611376d23788
linuxlinux>= d1e879ec600f9b3bdd253167533959facfefb17b < 92cee08dc4f00e77fd1317e4343c5d458b0abab792cee08dc4f00e77fd1317e4343c5d458b0abab7
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel——
linuxlinux_kernel>= 6.15 < 6.18.346.18.34
linuxlinux_kernel>= 6.19 < 7.0.117.0.11
ubuntulinux-aws——
ubuntulinux-azure——
ubuntulinux-azure-7.0——
ubuntulinux-azure-fde——
ubuntulinux-gcp-7.0——
ubuntulinux-ibm——
ubuntulinux-nvidia——
ubuntulinux-nvidia-7.0——
ubuntulinux-nvidia-bos——
ubuntulinux-oracle——
ubuntulinux-oracle-7.0——
ubuntulinux-raspi——

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_redhat9.8CRITICAL
vendor_ubuntu9.1CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.