CVE-2026-43077 is a Linux kernel vulnerability in the crypto algif_aead interface. During AEAD decryption, the minimum receive-buffer size validation failed to include the authentication tag length in its calculation. As a result, the algif_aead decryption path could accept an undersized receive buffer because the required extra length for the tag was omitted from the check. The issue was fixed by correcting the size validation to add the missing tag-related length during decryption. The weakness is consistent with an incorrect calculation of buffer size.
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.
56 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel algif_aead cryptographic interface flaw involving an insufficient minimum receive-size check during decryption.
Linux kernel algif_aead decryption receive-size validation flaw.
Linux kernel ALGIF AEAD cryptographic-interface flaw involving insufficient minimum receive-size validation during decryption.
Linux kernel AF_ALG AEAD cryptographic interface flaw in the minimum receive-size validation for decryption.
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.