Linux kernel crypto CAAM DMA corruption on long HMAC keys
CVE-2026-43044 is a local Linux kernel vulnerability in the crypto CAAM component when processing HMAC keys longer than the hash block size. In this code path, the supplied key is first copied and then hashed into the effective key. The implementation correctly computed a DMA cache-aligned size for the temporary key buffer, but failed to use that rounded size for the actual allocation. As a result, the hashed key operation could write past the end of the allocated buffer and corrupt adjacent memory due to improper DMA cache alignment handling. The issue was fixed by replacing kmemdup with kmalloc for a sufficiently large buffer and then copying the key with memcpy.
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
5 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.