CVE-2023-52800 is an improper resource-locking flaw in the Linux kernel ath11k Wi-Fi driver. HTT packet-log handling accesses active physical-device state through ath11k_mac_get_ar_by_pdev_id() without entering an RCU read-side critical section, despite that state being RCU-protected. Concurrent removal or reclamation of the referenced device can therefore create a use-after-free condition. The issue was introduced in Linux kernel 5.6 and affects the ath11k receive-path implementation.
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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel ath11k Wi-Fi packet-log locking flaw.
A resolved Linux kernel Wi-Fi driver vulnerability affecting ath11k HTTP packet-log locking. An automated assessment characterized the likely impact as moderate and flagged characteristics including remote reachability, locking, simple fix, and potential use-after-free.
A Linux kernel ath11k Wi-Fi driver locking flaw in HTTP packet-log handling. Missing RCU read-side critical-section protection could result in a use-after-free condition and local availability impact, including instability or a crash.
A Linux kernel ath11k Wi-Fi driver vulnerability in HTTP packet-log handling. Missing RCU read-side critical-section protection could result in a use-after-free condition.
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.