Loading vulnerability…
CVE-2021-3744 is a resource-leak vulnerability in the Linux kernel AMD CCP cryptographic driver, in ccp_run_aes_gcm_cmd() within drivers/crypto/ccp/ccp-ops.c. Error-handling paths during AES-GCM command setup do not correctly release allocated resources. Specifically, failures initializing source data can leave AAD resources allocated, and cleanup-path errors can leave final work-area or authentication-tag resources unreleased. The resulting repeated memory consumption can exhaust system resources. The upstream correction is the patch titled “crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd,” available beginning in Linux v5.15-rc4.
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 crypto CCP resource-leak vulnerability in AES-GCM command handling.
Linux kernel CCP crypto-component resource-leak vulnerability in ccp_run_aes_gcm_cmd().
Linux kernel AMD CCP cryptographic-driver resource-leak flaw in ccp_run_aes_gcm_cmd().
Linux kernel CCP cryptographic-driver resource-leak issue in AES-GCM command 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.