CVE-2026-64176

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: iwlwifi: mvm: fix driver-set TX rates on old devices<br /> <br /> On old devices such as 7265D, rates are still encoded in version 1<br /> format, which doesn&amp;#39;t use the CCK/OFDM rate index (0-3/0-7) but<br /> rather their PLCP value (e.g. 10 for 1 Mbps CCK rate.)<br /> <br /> While introducing v3 rates, I changed the driver from internally<br /> handling v1 rates and converting to v2, to internally handling v3<br /> and converting to v1 or v2 according to the firmware. I accordingly<br /> changed the code in iwl_mvm_mac80211_idx_to_hwrate() to no longer<br /> have different values for different APIs. This was correct.<br /> <br /> However, I later reverted this part of the change, because it was<br /> reported that I had broken beacon rates, causing a FW assert/crash.<br /> This caused TX_CMD rates to be set incorrectly, potentially causing<br /> a warning when reported back from the device as having been used.<br /> <br /> Fix this (hopefully correctly now) by handling beacon rates in the<br /> TX_CMD that&amp;#39;s embedded in the beacon template command separately.<br /> Restore iwl_mvm_mac80211_idx_to_hwrate() to return only the rate<br /> index, not PLCP value, fixing the real TX_CMD.