CVE-2026-64175
Description
A flaw was found in the Linux kernel's iwlwifi driver. When the Wi-Fi firmware crashes, the driver continues to process network transmission requests inefficiently. This creates a continuous loop of attempting to send data through an unresponsive firmware, consuming excessive CPU resources and memory. This can lead to resource exhaustion and a denial of service (DoS) for the system.
Mitigation
To mitigate this issue, the `iwlwifi` kernel module can be blacklisted to prevent it from loading. This will disable Wi-Fi functionality on the system.
To blacklist the module:
1. Create a file `/etc/modprobe.d/blacklist-iwlwifi.conf` with the following content:
blacklist iwlwifi2. Regenerate the initramfs:
bashor
sudo dracut -f -v
bash3. Reboot the system for the changes to take effect.
sudo mkinitrd -f -v /boot/initramfs-$(uname -r).img $(uname -r)
Note that disabling the `iwlwifi` module will prevent the use of Intel Wi-Fi devices.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.3 | N/A | 7.5 |
| Attack Vector | Adjacent Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Amplification
An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
