Loading vulnerability…
CVE-2023-52594 is an out-of-bounds read vulnerability in the Linux kernel ath9k Wi-Fi driver's ath9k_htc_txstatus() function. The function processes transmit-status data supplied by a USB device through a USB Request Block (URB). When the device-supplied txs->cnt exceeds HTC_MAX_TX_STATUS, processing can read beyond the txs->txstatus array. An existing WARN_ON() detects the invalid count but does not stop processing. The fix returns immediately when the count exceeds the array capacity. The issue was discovered using a modified version of syzkaller and demonstrated by an undefined-behavior sanitizer report.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Referenced by the OpenShift Container Platform 4.17.30 security advisory without vulnerability-specific technical details.
Linux kernel ath9k Wi-Fi driver potential array-index out-of-bounds read vulnerability.
Linux kernel ath9k Wi-Fi driver potential out-of-bounds read.
A potential array-index-out-of-bounds read in the Linux kernel ath9k Wi-Fi driver function ath9k_htc_txstatus().
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.