CVE-2023-54300

wifi: ath9k: avoid referencing uninit memory in ath9k_wmi_ctrl_rx

N/A
Published: December 30, 2025 at 12:23 PM UTC
Updated: June 17, 2026 at 06:47 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: avoid referencing uninit memory in ath9k_wmi_ctrl_rx For the reasons also described in commit b383e8abed41 ("wifi: ath9k: avoid uninit memory read in ath9k_htc_rx_msg()"), ath9k_htc_rx_msg() should validate pkt_len before accessing the SKB. For example, the obtained SKB may have been badly constructed with pkt_len = 8. In this case, the SKB can only contain a valid htc_frame_hdr but after being processed in ath9k_htc_rx_msg() and passed to ath9k_wmi_ctrl_rx() endpoint RX handler, it is expected to have a WMI command header which should be located inside its data payload. Implement sanity checking inside ath9k_wmi_ctrl_rx(). Otherwise, uninit memory can be referenced. Tested on Qualcomm Atheros Communications AR9271 802.11n . Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.35 ≤ v < 4.14.3222.6.35 ≤ v < 4.19.2912.6.35 ≤ v < 5.10.1882.6.35 ≤ v < 5.15.1212.6.35 ≤ v < 5.4.2512.6.35 ≤ v < 6.1.392.6.35 ≤ v < 6.3.132.6.35 ≤ v < 6.4.42.6.35 ≤ v < 6.52.6.35fb9987d0f748c983bb795a86f47522313f701a08
Vendor states this is fixed in 0bc12e41af4e3ae1f0efecc377f0514459df0707 (fixed)
Vendor states this is fixed in 250efb4d3f5b32a115ea6bf25437ba44a1b3c04f (fixed)
Vendor states this is fixed in 28259ce4f1f1f9ab37fa817756c89098213d2fc0 (fixed)
Vendor states this is fixed in 75acec91aeaa07375cd5f418069e61b16d39bbad (fixed)
Vendor states this is fixed in 8ed572e52714593b209e3aa352406aff84481179 (fixed)
Vendor states this is fixed in 90e3c10177573b8662ac9858abd9bf731d5d98e0 (fixed)
Vendor states this is fixed in ad5425e70789c29b93acafb5bb4629e4eb908296 (fixed)
Vendor states this is fixed in d1c2ff2bd84c3692c9df267a2b991ce92bfca8ef (fixed)
Vendor states this is fixed in f24292e827088bba8de7158501ac25a59b064953 (fixed)
Vendor states this is fixed in 2.6.35 (unaffected)
Vendor states this is fixed in 4.14.322 (unaffected)
Vendor states this is fixed in 4.19.291 (unaffected)
Vendor states this is fixed in 5.10.188 (unaffected)
Vendor states this is fixed in 5.15.121 (unaffected)
Vendor states this is fixed in 5.4.251 (unaffected)
Vendor states this is fixed in 6.1.39 (unaffected)
Vendor states this is fixed in 6.3.13 (unaffected)
Vendor states this is fixed in 6.4.4 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card