CVE-2026-93799

8.8

Linux · Kernel

The Linux kernel contains an out-of-bounds memory access vulnerability in the iwlwifi wireless driver, which can be triggered by a malicious firmware notification.

Executive summary

The Linux kernel is vulnerable to an out-of-bounds memory access flaw in the iwlwifi driver that could allow a remote attacker to compromise system integrity or cause a denial of service.

Vulnerability

This vulnerability occurs in the iwlwifi mvm component, where the system fails to validate a 5-bit station identifier (sta_id) extracted from a firmware notification. An unauthenticated attacker on the local network can exploit this lack of bounds checking to index the fw_id_to_mac_id array out of bounds.

Business impact

The successful exploitation of this vulnerability can lead to unauthorized memory access, potentially resulting in system crashes, denial of service, or the execution of arbitrary code within the kernel context. With a CVSS score of 8.8, this flaw represents a significant risk to organizational infrastructure, particularly for systems relying on affected Wi-Fi hardware.

Remediation

Immediate Action: Update the Linux kernel to version 6.12.111, 6.18.53, or later to incorporate the necessary bounds checking validation.

Proactive Monitoring: Monitor system logs for kernel panics or unusual iwlwifi driver behavior, which may indicate attempted exploitation of this memory corruption flaw.

Compensating Controls: Restrict wireless network access to trusted devices and ensure that wireless firmware is sourced only from verified, secure channels to minimize the risk of malicious firmware notifications.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the severity of this kernel-level vulnerability, administrators should prioritize patching affected systems during the next maintenance cycle. Applying the validated kernel updates is the only definitive way to mitigate the risk of out-of-bounds memory access and ensure the continued stability and security of the affected environment.

More Linux CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources