CVE-2023-54300 — wifi: ath9k: avoid referencing uninit memory in ath9k_wmi_ctrl_rx
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ fb9987d0f748c983bb795a86f47522313f701a08 and < 0bc12e41af4e3ae1f0efecc377f0514459df0707≥ fb9987d0f748c983bb795a86f47522313f701a08 and < 28259ce4f1f1f9ab37fa817756c89098213d2fc0≥ fb9987d0f748c983bb795a86f47522313f701a08 and < 90e3c10177573b8662ac9858abd9bf731d5d98e0≥ fb9987d0f748c983bb795a86f47522313f701a08 and < 250efb4d3f5b32a115ea6bf25437ba44a1b3c04f≥ fb9987d0f748c983bb795a86f47522313f701a08 and < ad5425e70789c29b93acafb5bb4629e4eb908296≥ fb9987d0f748c983bb795a86f47522313f701a08 and < d1c2ff2bd84c3692c9df267a2b991ce92bfca8ef≥ fb9987d0f748c983bb795a86f47522313f701a08 and < 8ed572e52714593b209e3aa352406aff84481179≥ fb9987d0f748c983bb795a86f47522313f701a08 and < 75acec91aeaa07375cd5f418069e61b16d39bbad and 2 more≥ fb9987d0f748c983bb795a86f47522313f701a08 and < f24292e827088bba8de7158501ac25a59b064953version 2.6.35 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.23%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- git.kernel.org/stable/c/8ed572e52714593b209e3aa352406aff84481179
- git.kernel.org/stable/c/f24292e827088bba8de7158501ac25a59b064953
- git.kernel.org/stable/c/250efb4d3f5b32a115ea6bf25437ba44a1b3c04f
- git.kernel.org/stable/c/28259ce4f1f1f9ab37fa817756c89098213d2fc0
- git.kernel.org/stable/c/ad5425e70789c29b93acafb5bb4629e4eb908296
- git.kernel.org/stable/c/90e3c10177573b8662ac9858abd9bf731d5d98e0
- git.kernel.org/stable/c/0bc12e41af4e3ae1f0efecc377f0514459df0707
- git.kernel.org/stable/c/75acec91aeaa07375cd5f418069e61b16d39bbad
- git.kernel.org/stable/c/d1c2ff2bd84c3692c9df267a2b991ce92bfca8ef
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-54300 is "wifi: ath9k: avoid referencing uninit memory in ath9k_wmi_ctrl_rx", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.