CVE-2026-64176

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

wifi: iwlwifi: mvm: fix driver-set TX rates on old devices

On old devices such as 7265D, rates are still encoded in version 1 format, which doesn't use the CCK/OFDM rate index (0-3/0-7) but rather their PLCP value (e.g. 10 for 1 Mbps CCK rate.)

While introducing v3 rates, I changed the driver from internally handling v1 rates and converting to v2, to internally handling v3 and converting to v1 or v2 according to the firmware. I accordingly changed the code in iwl_mvm_mac80211_idx_to_hwrate() to no longer have different values for different APIs. This was correct.

However, I later reverted this part of the change, because it was reported that I had broken beacon rates, causing a FW assert/crash. This caused TX_CMD rates to be set incorrectly, potentially causing a warning when reported back from the device as having been used.

Fix this (hopefully correctly now) by handling beacon rates in the TX_CMD that's embedded in the beacon template command separately. Restore iwl_mvm_mac80211_idx_to_hwrate() to return only the rate index, not PLCP value, fixing the real TX_CMD.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
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: mvm: fix driver-set TX rates on old devices - kernel/git/stable/linux.git - Linux kernel stable tree

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

wifi: iwlwifi: mvm: fix driver-set TX rates on old devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fe92651b44fd3cfc8dcfdaad0e82885c384dada
generic

wifi: iwlwifi: mvm: fix driver-set TX rates on old devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b58a79f2cd98156856eb49e8b55db5facdd7e6d

Vendor Advisories for CVE-2026-64176(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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-64176?
CVE-2026-64176 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix driver-set TX rates on old devices On old devices such as 7265D, rates are still encoded in version 1 format, which doesn't use the CCK/OFDM rate index (0-3/0-7) but rather their PLCP value (e.g. 10 for 1…
When was CVE-2026-64176 disclosed?
CVE-2026-64176 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-64176 actively exploited?
CVE-2026-64176 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 89.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64176?
CVE-2026-64176 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-64176?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64176, 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-64176

Explore →

Is Your Infrastructure Affected by CVE-2026-64176?

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

Start Free Scan →Browse All CVEs