CVE-2026-97442
Description
A flaw was found in the Linux kernel's ath11k wireless driver. When processing incoming Wi-Fi frames, the driver fails to properly validate native Wi-Fi header lengths, allowing packets that exceed expected limits to be processed. An attacker within wireless range could exploit this issue by transmitting crafted Wi-Fi frames, triggering invalid memory access and kernel stack corruption. This flaw primarily results in a system crash, causing a Denial of Service (DoS).
Statement
A flaw was found in the Linux kernel's ath11k wireless driver, which affects Red Hat Enterprise Linux 8, 9, and 10 (including the kernel-rt variant), Red Hat In-Vehicle OS, and the RHEL CoreOS images used by OpenShift Container Platform. This moderate-impact flaw exists because the ath11k_dp_rx_h_undecap_nwifi() function does not validate that a received packet's native Wi-Fi decapsulation header fits within the maximum expected header length. An attacker within radio range of a system using affected ath11k-based Wi-Fi hardware can transmit crafted Wi-Fi frames with an oversized native Wi-Fi header, causing the driver to access and modify out-of-bounds header data. The resulting memory corruption manifests as kernel stack corruption and a system crash, so the primary impact is denial of service. Red Hat Enterprise Linux 6 and 7 are not affected because the vulnerable code is not present in those kernel versions. Fixes for the affected streams are currently deferred: the issue is an input-validation bug in the Wi-Fi receive path whose demonstrated impact is limited to availability, with no evidence of privilege escalation, information disclosure, or controlled data modification, so the fix is planned for delivery via a future scheduled kernel update rather than an immediate out-of-band update; the residual risk is that an adjacent wireless attacker can crash systems equipped with affected ath11k hardware until the fix is applied. Red Hat has rated this flaw as Moderate severity (CVSS 3.1 score of 5.5), which is lower than the Important rating (8.8) in the upstream CVE record; the difference stems from the upstream vector assuming an unauthenticated adjacent attacker with high confidentiality and integrity impact, whereas Red Hat's assessment reflects availability-only impact from the demonstrated kernel crash.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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 | 5.5 | N/A | 8.8 |
| Attack Vector | Local | N/A | Adjacent 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 | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.