Loading vulnerability…
CVE-2023-53373 is a use-after-free vulnerability in the Linux kernel's crypto seqiv implementation. seqiv treated EINPROGRESS as an asynchronous return condition, but freed request-related data for other return values. When a caller specifies MAY_BACKLOG, a backlogged request may return EBUSY; because EBUSY was not handled equivalently to EINPROGRESS, seqiv could prematurely free data still associated with the request. The fix handles EBUSY in the same manner as EINPROGRESS.
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.
24 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel crypto seqiv vulnerability concerning correct handling of EBUSY, addressed by the Rocky Linux 9 security update advisory CRLSA-2025_17760.
Referenced by the TuxCare CentOS 8.5 security advisory; no vulnerability details are provided.
A Linux kernel crypto seqiv error-handling flaw involving EBUSY conditions.
Linux kernel crypto seqiv error-handling flaw involving EBUSY 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.