CVE-2026-64176
Last modified
CVE-2026-64176 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 3592c0083fb29cca13cd9978b8844d58b4eff548, < 6fe92651b44fd3cfc8dcfdaad0e82885c384dada; >= 3592c0083fb29cca13cd9978b8844d58b4eff548, < 6b58a79f2cd98156856eb49e8b55db5facdd7e6d; >= 3592c0083fb29cca13cd9978b8844d58b4eff548, < fb84b5cbcaab3ca0f4e961d92a40ed7f3aac483b; c6c14c2b08e9c4c82e1ec39ef3e8b9ec845ac7fd; >= 6.17.9, < 6.18 |
| Linux | Linux | 6.18 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64176?
How severe is CVE-2026-64176?
How do I fix CVE-2026-64176?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64170In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64171In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64172In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64173In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64174In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64175In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64177In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64178In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64179In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6418An issue was discovered in the Shared Account Synchronizatio…4.9
- CVE-2026-64180In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64181In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64176?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
