CVE-2026-64176
iwlwifi mvm driver sets incorrect TX rates on older Intel devices, causing FW warnings/crashes
Is CVE-2026-64176 being exploited?
Not confirmed. CVE-2026-64176 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-64176?
CVE-2026-64176 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64176?
Yes. A fix has been recorded for CVE-2026-64176. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64176 affect?
CVE-2026-64176 affects Linux kernel iwlwifi (mvm) driver, Older Intel wireless cards (e.g., 7265D), Linux hosts using affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64176?
Upgrade to the patched Linux kernel and update wireless firmware; reboot affected systems.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Incorrect TX_CMD rate encoding can trigger firmware assert/crash, causing wireless DoS and connectivity instability.
Patch when possible
- affected>= 3592c0083fb29cca13cd9978b8844d58b4eff548 and < 6fe92651b44fd3cfc8dcfdaad0e82885c384dada
- affected>= 3592c0083fb29cca13cd9978b8844d58b4eff548 and < 6b58a79f2cd98156856eb49e8b55db5facdd7e6d
- affected>= 3592c0083fb29cca13cd9978b8844d58b4eff548 and < fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b
- affectedc6c14c2b08e9c4c82e1ec39ef3e8b9ec845ac7fd
- affected>= 6.17.9 and < 6.18
- affected6.18
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.