Loading vulnerability…
CVE-2023-52813 is an error-handling vulnerability in the Linux kernel pcrypt cryptography component. When padata_do_parallel() encounters PADATA_RESET during parallel-data replacement, it returns -EBUSY without arranging an AEAD request completion callback. The test_aead_vec_cfg() caller interprets this return status as requiring a completion wait, leaving it blocked indefinitely because aead_request_complete() is never called. The resulting hung task can cause a kernel panic.
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.
Referenced by the OpenShift Container Platform 4.17.30 security advisory without vulnerability-specific technical details.
A hung-task condition in the Linux kernel pcrypt cryptographic component during PADATA_RESET.
A Linux kernel pcrypt crypto subsystem flaw that can cause a hung task during PADATA_RESET handling.
Linux kernel pcrypt PADATA_RESET hung-task vulnerability.
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.