{"id":"CVE-2026-64176","title":"wifi: iwlwifi: mvm: fix driver-set TX rates on old devices","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: fix driver-set TX rates on old devices\n\nOn old devices such as 7265D, rates are still encoded in version 1\nformat, which doesn't use the CCK/OFDM ra…","severity":"high","cvss":8.1,"cvssVector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= 3592c0083fb29cca13cd9978b8844d58b4eff548 < 6fe92651b44fd3cfc8dcfdaad0e82885c384dada","Linux >= 3592c0083fb29cca13cd9978b8844d58b4eff548 < 6b58a79f2cd98156856eb49e8b55db5facdd7e6d","Linux >= 3592c0083fb29cca13cd9978b8844d58b4eff548 < fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b","Linux c6c14c2b08e9c4c82e1ec39ef3e8b9ec845ac7fd","Linux >= 6.17.9 < 6.18","Linux 6.18"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-10-16T15:37:13.733939Z"},"published":"2026-07-19","updated":"2026-10-16","sourceUpdated":"2026-10-16T15:42:25.453Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-64176","references":[{"url":"https://git.kernel.org/stable/c/6fe92651b44fd3cfc8dcfdaad0e82885c384dada"},{"url":"https://git.kernel.org/stable/c/6b58a79f2cd98156856eb49e8b55db5facdd7e6d"},{"url":"https://git.kernel.org/stable/c/fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b"}],"tags":["cve.org"],"epss":0.00209,"epssPercentile":0.10409,"ingestedAt":"2026-10-16T17:24:46.808Z","slug":"CVE-2026-64176","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: fix driver-set TX rates on old devices\n\nOn old devices such as 7265D, rates are still encoded in version 1\nformat, which doesn't use the CCK/OFDM rate index (0-3/0-7) but\nrather their PLCP value (e.g. 10 for 1 Mbps CCK rate.)\n\nWhile introducing v3 rates, I changed the driver from internally\nhandling v1 rates and converting to v2, to internally handling v3\nand converting to v1 or v2 according to the firmware. I accordingly\nchanged the code in iwl_mvm_mac80211_idx_to_hwrate() to no longer\nhave different values for different APIs. This was correct.\n\nHowever, I later reverted this part of the change, because it was\nreported that I had broken beacon rates, causing a FW assert/crash.\nThis caused TX_CMD rates to be set incorrectly, potentially causing\na warning when reported back from the device as having been used.\n\nFix this (hopefully correctly now) by handling beacon rates in the\nTX_CMD that's embedded in the beacon template command separately.\nRestore iwl_mvm_mac80211_idx_to_hwrate() to return only the rate\nindex, not PLCP value, fixing the real TX_CMD.\n\n## Affected\n\n- `Linux >= 3592c0083fb29cca13cd9978b8844d58b4eff548 < 6fe92651b44fd3cfc8dcfdaad0e82885c384dada`\n- `Linux >= 3592c0083fb29cca13cd9978b8844d58b4eff548 < 6b58a79f2cd98156856eb49e8b55db5facdd7e6d`\n- `Linux >= 3592c0083fb29cca13cd9978b8844d58b4eff548 < fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b`\n- `Linux c6c14c2b08e9c4c82e1ec39ef3e8b9ec845ac7fd`\n- `Linux >= 6.17.9 < 6.18`\n- `Linux 6.18`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":45,"depthScoreParts":{"impact":44.6,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}