Kernel memory read via oversized USB status count
Published Mar 6, 2024 · Updated May 11, 2026
Out-of-bounds read in the Linux kernel ath9k driver allows local users to trigger a kernel memory read through malformed USB status data. ath9k_htc_txstatus trusts the USB URB-derived txs->cnt after WARN_ON and indexes beyond the 12-element txs->txstatus array instead of returning. Reachability requires local access to a host using the ath9k HTC USB driver, and the invalid kernel read can expose memory or interrupt system operation.
Summary
What happened
Out-of-bounds read in the Linux kernel ath9k driver allows local users to trigger a kernel memory read through malformed USB status data. ath9k_htc_txstatus trusts the USB URB-derived txs->cnt after WARN_ON and indexes beyond the 12-element txs->txstatus array instead of returning. Reachability requires local access to a host using the ath9k HTC USB driver, and the invalid kernel read can expose memory or interrupt system operation.
The record
- CVE
- CVE-2023-52594
- Published
- Mar 6, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-129, T1200
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=27876a29de221186c9d5883e5fe5f6da18ef9a45 <25c6f49ef59b7a9b80a3f7ab9e95268a1b01a234
- Affected versionversion=27876a29de221186c9d5883e5fe5f6da18ef9a45 <2adc886244dff60f948497b59affb6c6ebb3c348
- Affected versionversion=27876a29de221186c9d5883e5fe5f6da18ef9a45 <84770a996ad8d7f121ff2fb5a8d149aad52d64c1
- Affected versionversion=27876a29de221186c9d5883e5fe5f6da18ef9a45 <9003fa9a0198ce004b30738766c67eb7373479c9
- Affected versionversion=27876a29de221186c9d5883e5fe5f6da18ef9a45 <be609c7002dd4504b15b069cb7582f4c778548d1
- Affected versionversion=27876a29de221186c9d5883e5fe5f6da18ef9a45 <e4f4bac7d3b64eb75f70cd3345712de6f68a215d
- Affected versionversion=27876a29de221186c9d5883e5fe5f6da18ef9a45 <f11f0fd1ad6c11ae7856d4325fe9d05059767225
- Affected versionversion=27876a29de221186c9d5883e5fe5f6da18ef9a45 <f44f073c78112ff921a220d01b86d09f2ace59bc
- Affected versionversion=3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo