Loading vulnerability…
CVE-2021-43267 is a heap-based buffer overflow in the Linux kernel TIPC subsystem, specifically in net/tipc/crypto.c in the function tipc_crypto_key_rcv(). The flaw affects kernels before 5.14.16 and, per the provided supporting content, impacts versions from 5.10-rc1 through 5.15. The bug is in processing TIPC MSG_CRYPTO messages: the kernel allocates memory based on the received MSG_CRYPTO payload size, then reads an attacker-controlled key length field from the embedded tipc_aead_key structure and performs memcpy operations on alg_name and key material before validating that the supplied key length is consistent with the actual payload size. This insufficient validation allows an attacker to craft a message with a small declared payload/allocation size but a larger keylen, causing a heap overflow in kernel memory.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously disclosed TIPC-related Linux kernel vulnerability referenced for background and related research; described here as a remote Linux kernel heap overflow.
A heap overflow vulnerability in the Linux kernel's TIPC module that can be exploited locally or remotely within a network to gain kernel privileges and potentially fully compromise the system.
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.