SEPTEMBER 7, 2026
Live Feed
Back to database
Case File

CVE-2026-64176

HIGH · CVSS 8.1 EPSS 0.21%

Source: NVD + CISA KEV + EPSS · Published 2026-07-19 · Last synced 2026-08-18

CyberRota Analysis

AI-Generated

The vulnerability affects the iwlwifi driver in the Linux kernel, specifically impacting older devices like the 7265D, where transmission rates are incorrectly set due to a mishandling of rate encoding. This flaw can lead to improper transmission rates being reported, potentially causing firmware crashes and degraded wireless performance. Organizations using affected Linux systems, particularly those relying on older Wi-Fi hardware, should prioritize applying the fix to mitigate the risk of operational disruptions.

CVE
CVE-2026-64176
Severity
HIGH
CVSS
8.1
EPSS
0.21%
Linux

Original NVD 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.

Related CVEs

Other vulnerabilities affecting the same vendor(s)