CVE-2026-64175

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 13, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

wifi: iwlwifi: mld: stop TX during firmware restart - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dc31c69476520bb4c2a208211a8d3c310a62c4d0
generic

wifi: iwlwifi: mld: stop TX during firmware restart - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2becb38a3e217ef2b2f42fddd7db7a25905ec291
generic

wifi: iwlwifi: mld: stop TX during firmware restart - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13f1786395dbbf3df73337063c798f1266be6151

Vendor Advisories for CVE-2026-64175(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 29× in last 7d / 154× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 789 total refreshes for this CVE.

  1. 2026-08-30 02:44 UTCEG score recompute
  2. 2026-08-30 02:44 UTCVendor advisory
  3. 2026-08-30 02:44 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 02:58 UTCEG score recompute
  7. 2026-08-28 02:58 UTCVendor advisory
  8. 2026-08-28 02:58 UTCGHSA enrichment
  9. 2026-08-27 13:57 UTCVendor advisory
  10. 2026-08-27 13:57 UTCGHSA enrichment
  11. 2026-08-27 00:56 UTCEG score recompute
  12. 2026-08-27 00:56 UTCVendor advisory
  13. 2026-08-27 00:56 UTCGHSA enrichment
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-26 11:54 UTCVendor advisory
  16. 2026-08-26 11:54 UTCGHSA enrichment
  17. 2026-08-25 22:48 UTCEG score recompute
  18. 2026-08-25 22:48 UTCVendor advisory
  19. 2026-08-25 22:48 UTCGHSA enrichment
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 09:48 UTCVendor advisory
  22. 2026-08-25 09:47 UTCGHSA enrichment
  23. 2026-08-24 20:46 UTCEG score recompute
  24. 2026-08-24 20:46 UTCVendor advisory
  25. 2026-08-24 20:46 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 07:45 UTCVendor advisory
  2. 2026-08-24 07:45 UTCGHSA enrichment
  3. 2026-08-23 18:21 UTCVendor advisory
  4. 2026-08-23 18:21 UTCGHSA enrichment
  5. 2026-08-23 05:20 UTCEG score recompute
  6. 2026-08-23 05:20 UTCVendor advisory
  7. 2026-08-23 05:20 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 16:19 UTCVendor advisory
  10. 2026-08-22 16:19 UTCGHSA enrichment
  11. 2026-08-22 03:18 UTCEG score recompute
  12. 2026-08-22 03:18 UTCVendor advisory
  13. 2026-08-22 03:18 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 14:17 UTCVendor advisory
  16. 2026-08-21 14:17 UTCGHSA enrichment
  17. 2026-08-21 01:16 UTCEG score recompute
  18. 2026-08-21 01:16 UTCVendor advisory
  19. 2026-08-21 01:15 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 12:14 UTCVendor advisory
  22. 2026-08-20 12:14 UTCGHSA enrichment
  23. 2026-08-19 22:55 UTCEG score recompute
  24. 2026-08-19 22:55 UTCVendor advisory
  25. 2026-08-19 22:55 UTCGHSA enrichment
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 08:39 UTCVendor advisory
  28. 2026-08-19 08:39 UTCGHSA enrichment
  29. 2026-08-18 19:39 UTCEG score recompute
  30. 2026-08-18 19:39 UTCVendor advisory
  31. 2026-08-18 19:39 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-18 01:49 UTCEG score recompute
  34. 2026-08-18 01:49 UTCVendor advisory
  35. 2026-08-18 01:49 UTCGHSA enrichment
  36. 2026-08-17 13:47 UTCEPSS rescore
  37. 2026-08-17 11:22 UTCVendor advisory
  38. 2026-08-17 11:22 UTCGHSA enrichment
  39. 2026-08-16 22:21 UTCEG score recompute
  40. 2026-08-16 22:21 UTCVendor advisory
  41. 2026-08-16 22:21 UTCGHSA enrichment
  42. 2026-08-16 14:56 UTCEPSS rescore
  43. 2026-08-16 09:19 UTCEG score recompute
  44. 2026-08-16 09:19 UTCVendor advisory
  45. 2026-08-16 09:19 UTCGHSA enrichment
  46. 2026-08-15 20:19 UTCVendor advisory
  47. 2026-08-15 20:19 UTCGHSA enrichment
  48. 2026-08-15 07:18 UTCEG score recompute
  49. 2026-08-15 07:18 UTCVendor advisory
  50. 2026-08-15 07:18 UTCGHSA enrichment
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-14 17:48 UTCVendor advisory
  53. 2026-08-14 17:48 UTCGHSA enrichment
  54. 2026-08-14 04:37 UTCEG score recompute
  55. 2026-08-14 04:37 UTCVendor advisory
  56. 2026-08-14 04:37 UTCGHSA enrichment
  57. 2026-08-13 22:00 UTCEPSS rescore
  58. 2026-08-13 15:36 UTCEG score recompute
  59. 2026-08-13 15:36 UTCVendor advisory
  60. 2026-08-13 15:36 UTCGHSA enrichment
  61. 2026-08-13 03:32 UTCVendor advisory
  62. 2026-08-13 03:32 UTCGHSA enrichment
  63. 2026-08-12 14:31 UTCEG score recompute
  64. 2026-08-12 14:31 UTCVendor advisory
  65. 2026-08-12 14:31 UTCGHSA enrichment
  66. 2026-08-12 13:51 UTCEPSS rescore
  67. 2026-08-12 01:30 UTCEG score recompute
  68. 2026-08-12 01:30 UTCVendor advisory
  69. 2026-08-12 01:30 UTCGHSA enrichment
  70. 2026-08-11 12:29 UTCEG score recompute
  71. 2026-08-11 12:29 UTCVendor advisory
  72. 2026-08-11 12:29 UTCGHSA enrichment
  73. 2026-08-11 00:00 UTCEPSS rescore
  74. 2026-08-10 23:28 UTCVendor advisory
  75. 2026-08-10 23:28 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64175?
CVE-2026-64175 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mld: stop TX during firmware restart When iwlwifi firmware crashes (e.g., NMIINTERRUPTUNKNOWN on Intel BE201/Wi-Fi 7), iwlmldnicerror() sets mld->fwstatus.inhwrestart to true. However, iwlmldtxfromtxq() does not…
When was CVE-2026-64175 disclosed?
CVE-2026-64175 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64175 actively exploited?
CVE-2026-64175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64175?
CVE-2026-64175 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-64175?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64175, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64175

Explore →

Is Your Infrastructure Affected by CVE-2026-64175?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.