Security Resilience

CVE-2026-64176

Linux Kernel 6.17.9 – 6.18

Published
19 July 2026
Modified
19 October 2026
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS Score 0.0027 19th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-64176 is a high-severity Incorrect Calculation (CWE-682) vulnerability in Linux Kernel. Its CVSS base score is 8.1 (High).

Operationally, ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-2163Same product: Linux Linux Kernel
CVE-2026-64006Same product: Linux Linux Kernel
CVE-2024-42231Same product: Linux Linux Kernel
CVE-2026-43030Same product: Linux Linux Kernel
CVE-2026-52920Same product: Linux Linux Kernel
CVE-2026-45933Same product: Linux Linux Kernel
CVE-2026-53217Same product: Linux Linux Kernel
CVE-2026-43009Same product: Linux Linux Kernel
CVE-2026-45988Same product: Linux Linux Kernel
CVE-2026-43321Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
6.18, 7.1 · 6.17.9 — 6.18 · 6.18.1 — 6.18.34 · 6.19 — 7.0.11

Mitigating Controls

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development and acceptance can detect calculation flaws before deployment.

prevents

Secure coding standards directly prohibit unsafe arithmetic and require defensive checks against incorrect results.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-682, a pillar-level weakness, and none of its children carries one either.

References