CVE-2026-43330: crypto: caam - fix overflow on long hmac keys
In the Linux kernel, the following vulnerability has been resolved:
crypto: caam - fix overflow on long hmac keys
When a key longer than block size is supplied, it is copied and then
hashed into the real key. The memory allocated for the copy needs to
be rounded to DMA cache alignment, as otherwise the hashed key may
corrupt neighbouring memory.
The copying is performed using kmemdup, however this leads to an overflow:
reading more bytes (aligned_len - keylen) from the keylen source buffer.
Fix this by replacing kmemdup with kmalloc, followed by memcpy.
Security readout for executives and security teams
Plain-English summary
CVE-2026-43330 is a Linux kernel flaw in the CAAM cryptographic driver. A local user or process could trigger memory corruption by using overly long HMAC keys. The reported impact is high because confidentiality, integrity, and availability may all be affected. No source provided indicates active exploitation.
Executive priority
Prioritize remediation in normal high-severity kernel patch cycles, faster for shared or security-sensitive systems. This is not currently evidenced as internet-exploited, but local kernel memory corruption can create serious business risk if abused after initial access.
Technical view
The CAAM crypto code mishandles HMAC keys longer than the block size. A kmemdup copy can read beyond the source buffer when DMA cache alignment padding is involved. The kernel fix replaces kmemdup with kmalloc plus memcpy to avoid the overflow condition.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with the CAAM crypto driver in use. The CVSS vector is local, low complexity, privileges required, and no user interaction. Exact distribution package impact requires vendor mapping.
Exploitation context
Sources rate this as CVSS 7.8 high with local authenticated access required. The bundle does not cite public exploitation, weaponized proof of concept, or CISA KEV listing. Treat as important for multi-user, appliance, and embedded Linux environments using this driver.
Researcher notes
The CVE record provides a clear root cause and stable kernel commit references, but no exploit status or detailed distro matrix. Validate exposure by driver presence and kernel lineage. Avoid assuming all Linux systems are affected without vendor-specific package confirmation.
Mitigation direction
Update to a Linux kernel version containing the referenced stable fixes.
Check your Linux distribution or device vendor advisory for packaged kernel updates.
Prioritize systems where the CAAM crypto driver is enabled or required.
If no update exists, ask the vendor for supported risk-reduction guidance.
Validation and detection
Inventory Linux kernel versions across affected fleets.
Check whether the CAAM crypto driver is present and enabled.
Map running kernels to vendor advisories and referenced stable commits.
Confirm patched kernels are installed and active after reboot.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43330 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
6Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.