CVE-2026-64037

published 19 Jul 2026 · updated 19 Oct 2026

wifi: iwlwifi: mld: fix TSO segmentation explosion when AMSDU is disabled

9.8CriticalCVSS 9.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 92cee08dc4f00e77fd1317e4343c5d458b0abab7, Kernel 9e360e610a73f62432e986775023d5382773f045 and Kernel cbe1c8245e4469d1aa6e12e5d913611376d23788.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.15, >=d1e879ec600f9b3bdd253167533959facfefb17b <92cee08dc4f00e77fd1317e4343c5d458b0abab7, >=d1e879ec600f9b3bdd253167533959facfefb17b <9e360e610a73f62432e986775023d5382773f045, >=d1e879ec600f9b3bdd253167533959facfefb17b <cbe1c8245e4469d1aa6e12e5d913611376d2378892cee08dc4f00e77fd1317e4343c5d458b0abab7, 9e360e610a73f62432e986775023d5382773f045, cbe1c8245e4469d1aa6e12e5d913611376d23788

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64037 severity on Zeptric[![CVE-2026-64037](https://zeptric.io/badge/cve/CVE-2026-64037.svg)](https://zeptric.io/cve/CVE-2026-64037)