Skip to main content
VulnerabilityPublished Updated

CVE-2026-64175: Linux kernel · wifi: iwlwifi: mld: stop TX during firmware restart

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in dc31c69476520bb4c2a208211a8d3c310a62c4d0, 13f1786395dbbf3df73337063c798f1266be6151, 2becb38a3e217ef2b2f42fddd7db7a25905ec291
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 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 Linux kernel to dc31c69476520bb4c2a208211a8d3c310a62c4d0, 13f1786395dbbf3df73337063c798f1266be6151 or 2becb38a3e217ef2b2f42fddd7db7a25905ec291.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ d1e879ec600f9b3bdd253167533959facfefb17b, < dc31c69476520bb4c2a208211a8d3c310a62c4d0
Fixed in
  • dc31c69476520bb4c2a208211a8d3c310a62c4d0
LinuxLinuxAffected
  • ≥ d1e879ec600f9b3bdd253167533959facfefb17b, < 13f1786395dbbf3df73337063c798f1266be6151
Fixed in
  • 13f1786395dbbf3df73337063c798f1266be6151
LinuxLinuxAffected
  • ≥ d1e879ec600f9b3bdd253167533959facfefb17b, < 2becb38a3e217ef2b2f42fddd7db7a25905ec291
Fixed in
  • 2becb38a3e217ef2b2f42fddd7db7a25905ec291
LinuxLinuxAffected
  • =6.15
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mld: stop TX during firmware restart When iwlwifi firmware crashes (e.g., NMI_INTERRUPT_UNKNOWN on Intel BE201/Wi-Fi 7), iwl_mld_nic_error() sets mld->fw_status.in_hw_restart to true. However, iwl_mld_tx_from_txq() does not check this flag before dequeuing frames from mac80211 and pushing them to the transport layer. Since the firmware is dead, iwl_trans_tx() returns -EIO for each frame, which then gets freed immediately. Under high-throughput conditions (e.g., Tailscale UDP traffic or active SSH sessions), this creates a tight dequeue-send-fail-free loop that wastes CPU cycles and generates rapid skb allocation churn, leading to memory pressure from slab fragmentation. The RX path already has this guard (iwl_mld_rx_mpdu checks in_hw_restart at rx.c:1906), and so does the TXQ allocation worker (iwl_mld_add_txqs_wk at tx.c:156). Add the same guard to iwl_mld_tx_from_txq() to stop all TX during firmware restart. Frames left in mac80211's TXQs are naturally drained after restart completes, when queue reallocation triggers iwl_mld_tx_from_txq() via iwl_mld_add_txq_list(), or when new upper-layer traffic invokes wake_tx_queue. Tested on ASUS Zenbook 14 UX3405CA with Intel BE201 (Wi-Fi 7) on kernel 6.19.5 where the firmware crashes approximately every 10-15 minutes under Tailscale traffic.

References

Community reviews

Loading reviews…