CVE-2026-52972 is an integer-overflow flaw in the Linux kernel crypto AF_ALG AEAD interface. Excessively large AEAD associated-data lengths can cause arithmetic overflow during transmit-buffer size validation, undermining the intended bounds check. The fix rejects associated-data lengths greater than 0x80000000 before the vulnerable size calculations occur.
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.
38 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Excessive AEAD associated-data length handling in the Linux kernel AF_ALG crypto interface.
Linux kernel AF_ALG AEAD associated-data length validation flaw.
Linux kernel AF_ALG cryptographic-interface vulnerability involving an insufficient bound on AEAD associated-data length.
Linux kernel AF_ALG AEAD vulnerability involving excessive associated-data length.
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.