CVE-2023-52801 is a use-after-free vulnerability in the Linux kernel iommufd subsystem. When iopt_area_split() splits an iopt_area that has populated a domain and is linked into domains_itree, its page-node entries were not properly reinserted into domains_itree. The resulting inconsistent interval-tree state can lead to use-after-free access during subsequent domain or I/O page-table operations.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel iommufd vulnerability involving a missing update of domains_itree after splitting iopt_area.
A resolved Linux kernel iommufd flaw involving failure to update domains_itree after an iopt_area is split. The automated assessment cited in the content characterizes the likely impact as moderate and identifies UAF-related patch indicators.
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.