Loading vulnerability…
CVE-2026-53016 is a memory-safety vulnerability in the Linux kernel crypto ccp component. The flaw affects AF_ALG requests using the rfc3686-ctr-aes-ccp skcipher path. In this scenario, the caller provides an 8-byte IV as exposed by the RFC3686 skcipher interface, but ccp_aes_complete() restores AES_BLOCK_SIZE bytes into the caller's IV buffer. Because AES_BLOCK_SIZE is 16 bytes, the function writes past the end of the provided IV buffer, resulting in an out-of-bounds write. The fix changes the code to use crypto_skcipher_ivsize() so that only the algorithm-specific IV length is copied back.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel crypto/ccp vulnerability related to copying the IV using skcipher ivsize.
A Linux kernel crypto/ccp vulnerability related to copying IV using skcipher ivsize.
A Linux kernel crypto subsystem vulnerability in ccp where IV restoration uses AES_BLOCK_SIZE instead of the skcipher IV size, causing a buffer overrun for AF_ALG rfc3686-ctr-aes-ccp requests.
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.