{ "schema_version": "1.6.1", "id": "RPI-CVE-2026-64176", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2026-64176" ], "published": "2026-07-19T15:41:06Z", "summary": "wifi: iwlwifi: mvm: fix driver-set TX rates on old devices", "details": "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 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.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:13", "name": "linux" }, "versions": [ "1:6.18.29-1+rpt1", "1:6.18.33-1+rpt1" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.18.29+rpt-rpi-2712", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-2712", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt", "binary_version": "1:6.18.33-1+rpt1" } ] }, "database_specific": { "per_version": { "1:6.18.29-1+rpt1": { "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc", "upstream_version": "6.18.29", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.34" }, "1:6.18.33-1+rpt1": { "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412", "upstream_version": "6.18.33", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.34" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2026-64176" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/6fe92651b44fd3cfc8dcfdaad0e82885c384dada" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/6b58a79f2cd98156856eb49e8b55db5facdd7e6d" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-05T13:16:28Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 8.1, "cvss_v3_severity": "High", "scenario": "AV:A - The vulnerable TX rate path is reached when the iwlwifi driver transmits WiFi management frames (probe responses, auth/assoc) or beacon templates in response to over-the-air activity. A remote attacker on the same WiFi/BSS segment can trigger this by sending probe requests to a victim AP or operating a rogue AP that causes victim clients to exchange management frames.\nAC:L - Once the victim uses affected legacy Intel hardware (e.g. 7265D with v1 rate firmware), the attacker can reliably trigger the bug by sending standard 802.11 management frames; no special timing, memory layout, or race conditions beyond normal WiFi traffic are required.\nPR:N - An adjacent attacker needs no privileges on the victim system. Exploitation is triggered purely by WiFi frames received by the victim's wireless interface; no local account, CAP_NET_ADMIN, or ioctl/netlink access on the victim is required.\nUI:N - From the attacker's perspective, no action by the victim user is needed beyond the WiFi interface being active (e.g., an AP broadcasting beacons or a client performing normal association). Probe responses and association handshakes are sent automatically by the driver.\nS:U - The vulnerability is confined to the iwlwifi kernel driver and its firmware interaction on the victim host. Impact does not cross a security boundary such as VM escape, sandbox escape, or IOMMU bypass.\nC:H - The double PLCP conversion passes PLCP values (e.g. 55, 110 for CCK rates) as array indices to iwl_fw_rate_idx_to_plcp(), which performs an unchecked lookup into a ~17-element table, causing out-of-bounds kernel memory reads whose results are embedded into TX commands.\nI:N - The bug corrupts rate-encoding metadata sent to firmware but does not provide an arbitrary kernel write, use-after-free, or demonstrated control-flow hijack primitive. Impact is malformed TX parameters and firmware misbehavior, not integrity of arbitrary kernel or user data.\nA:H - The fix commit and prior bug report document firmware assert/crash from incorrect beacon/TX_CMD rates on old devices, and the RX path emits WARN_ON for invalid rate values reported back from firmware. This can disable WiFi connectivity and potentially cause repeated firmware restart loops." } } }