Skip to main content
← All vulnerabilities
CVE-2026-64176

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 6.18, 6.18.34, 7.0.11
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • Linux 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 Linux

    6.18

  • KernelLinux

    From 6.18.0 · fixed in 6.18.34; From 6.19.0 · fixed in 7.0.11

References 3

git.kernel.org