CVE-2023-54300 json
wifi: ath9k: avoid referencing uninit memory in ath9k_wmi_ctrl_rx
published 10mo ago modified 4mo ago also EUVD-2023-60504
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 4.14.322, 4.19.291, 5.4.251, 5.10.188, 5.15.121, 6.1.39, 6.3.13, 6.4.4, 6.5
- linux Debian 12 6.1.52-1
- linux Debian 14, Debian 13 6.4.4-1
debian advisories DEBIAN-CVE-2023-54300
- linux Ubuntu 20.04 LTS 5.4.0-166.183
- linux Ubuntu 22.04 LTS 5.15.0-86.96
- linux-aws Ubuntu 20.04 LTS 5.4.0-1113.123
- linux-aws Ubuntu 22.04 LTS 5.15.0-1047.52
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1117.126
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1044.52
- linux-gke Ubuntu 22.04 LTS 5.15.0-1044.49
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1060.65
ubuntu advisories UBUNTU-CVE-2023-54300
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 8 4.18.0-513.5.1.el8_9
- perf RHEL 8 4.18.0-513.5.1.el8_9
- bpftool RHEL 8 4.18.0-513.5.1.el8_9
- kernel-core RHEL 8 4.18.0-513.5.1.el8_9
- kernel-tools RHEL 8 4.18.0-513.5.1.el8_9
- python3-perf RHEL 8 4.18.0-513.5.1.el8_9
- kernel-modules RHEL 8 4.18.0-513.5.1.el8_9
- kernel-zfcpdump RHEL 8 4.18.0-513.5.1.el8_9
red hat advisories RHSA-2023:7077RHSA-2023:6583
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-40.1
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.194.1
- kernel-syms SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-source SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 5.14.21-150400.24.194.1
- kernel-obs-build SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS +1 more 5.14.21-150400.24.194.1
- kernel-default-base SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +3 more 5.14.21-150400.24.194.1.150400.24.98.3
suse advisories SUSE-SU-2026:20845-1SUSE-SU-2026:20876-1SUSE-SU-2026:0617-1SUSE-SU-2026:20477-1SUSE-SU-2026:20498-1SUSE-SU-2026:0411-1
- git.kernel.org/stable/c/0bc12e41af4e3ae1f0efecc377f0514459df0707 commit
- git.kernel.org/stable/c/28259ce4f1f1f9ab37fa817756c89098213d2fc0 commit
- git.kernel.org/stable/c/90e3c10177573b8662ac9858abd9bf731d5d98e0 commit
- git.kernel.org/stable/c/250efb4d3f5b32a115ea6bf25437ba44a1b3c04f commit
- git.kernel.org/stable/c/ad5425e70789c29b93acafb5bb4629e4eb908296 commit
- git.kernel.org/stable/c/d1c2ff2bd84c3692c9df267a2b991ce92bfca8ef commit
- git.kernel.org/stable/c/8ed572e52714593b209e3aa352406aff84481179 commit
- git.kernel.org/stable/c/75acec91aeaa07375cd5f418069e61b16d39bbad commit
- git.kernel.org/stable/c/f24292e827088bba8de7158501ac25a59b064953 commit
Is CVE-2023-54300 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-54300 updated cvss 6.6
kernel: wifi: ath9k: avoid referencing uninit memory in ath9k_wmi_ctrl_rx
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +6 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: workaround, no fix available
-
Red Hat CodeReady Linux Builder (v. 8) kernel-debuginfo-common-x86_64 4.18.0-513.5.1.el8_9, kernel-debuginfo-common-aarch64 4.18.0-513.5.1.el8_9, kernel-debuginfo-common-ppc64le 4.18.0-513.5.1.el8_9 Red Hat Enterprise Linux BaseOS (v. 8) perf 4.18.0-513.5.1.el8_9, kernel 4.18.0-513.5.1.el8_9, bpftool 4.18.0-513.5.1.el8_9, kernel-core 4.18.0-513.5.1.el8_9, kernel-tools 4.18.0-513.5.1.el8_9, python3-perf 4.18.0-513.5.1.el8_9, +15 morefixed: vendor fix RHSA-2023:7077
-
Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-16).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/0bc12e41af4e3ae1f0efecc377f0514459df0707
- git.kernel.org /stable/c/28259ce4f1f1f9ab37fa817756c89098213d2fc0
- git.kernel.org /stable/c/90e3c10177573b8662ac9858abd9bf731d5d98e0
- git.kernel.org /stable/c/250efb4d3f5b32a115ea6bf25437ba44a1b3c04f
- git.kernel.org /stable/c/ad5425e70789c29b93acafb5bb4629e4eb908296
- git.kernel.org /stable/c/d1c2ff2bd84c3692c9df267a2b991ce92bfca8ef
- git.kernel.org /stable/c/8ed572e52714593b209e3aa352406aff84481179
- git.kernel.org /stable/c/75acec91aeaa07375cd5f418069e61b16d39bbad
- git.kernel.org /stable/c/f24292e827088bba8de7158501ac25a59b064953
Sources
- CVE List CVE-2023-54300
- NVD CVE-2023-54300
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.