Loading vulnerability…
CVE-2023-53494 is a use-after-free vulnerability in the Linux kernel XTS cryptographic-mode implementation. When an XTS request is submitted with MAY_BACKLOG, a return of EBUSY can indicate that the request has been queued for later processing. The vulnerable implementation handled EINPROGRESS as an asynchronous result but did not handle EBUSY equivalently, freeing request-related data even though the backlogged operation could still use it. The fix treats EBUSY like EINPROGRESS, preserving request state until asynchronous processing completes.
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.
A Linux kernel cryptographic XTS-mode issue involving incorrect handling of EBUSY.
Linux kernel crypto XTS error-handling flaw involving EBUSY handling.
Linux kernel crypto XTS error-handling flaw involving EBUSY conditions.
A Linux kernel cryptographic XTS handling flaw involving incorrect EBUSY error handling.
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.