Linux kernel CAAM long HMAC key overflow
CVE-2026-43330 is a Linux kernel vulnerability in the crypto CAAM subsystem's handling of HMAC keys longer than the hash block size. For oversized HMAC keys, the implementation copies the supplied key and hashes that copy into the effective key. The temporary buffer allocation needed to be rounded to DMA cache alignment to avoid corruption during hashing, but the vulnerable code performed the copy with kmemdup using the aligned allocation length rather than the original source length. As a result, the kernel could read past the end of the provided key buffer by aligned_len - keylen bytes. The associated hashing operation could also corrupt neighboring memory because of the alignment mismatch. The upstream fix replaces kmemdup with kmalloc followed by memcpy so that only the actual key length is copied while still allocating an appropriately aligned buffer.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.