LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43044: crypto: caam - fix DMA corruption on long hmac keys

In the Linux kernel, the following vulnerability has been resolved: crypto: caam - fix DMA corruption 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 rounding was performed, but never actually used for the allocation. Fix this by replacing kmemdup with kmalloc for a larger buffer, followed by memcpy.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux CAAM cryptographic-driver flaw can corrupt nearby kernel memory when processing an HMAC key longer than the algorithm’s block size. Successful abuse or accidental triggering could compromise confidentiality, integrity, or availability. Exposure depends on the affected driver and long-key processing path being available.

Executive priority

Treat as a high-priority kernel update for CAAM-enabled systems, especially shared or locally accessible appliances. First inventory affected configurations; deprioritize systems where the CAAM driver is absent or inactive.

Technical view

The CAAM driver allocates a copied HMAC key without applying the calculated DMA cache-aligned size. Hashing an oversized key may therefore overwrite adjacent memory. The supplied CVSS 3.1 vector scores 7.8 and describes local, low-complexity access requiring low privileges, without user interaction.

Likely exposure

Likely exposure is limited to systems running an affected Linux kernel with the CAAM crypto driver active and workloads able to supply oversized HMAC keys. The supplied version data is ambiguous, so kernel commit or distribution-advisory verification is necessary.

Exploitation context

The source bundle does not establish active exploitation, and the CVE is not listed as KEV. The supplied vector indicates a local attack path requiring low privileges. Whether an attacker can reach the vulnerable HMAC operation depends on system configuration and interfaces exposing CAAM cryptographic services.

Researcher notes

The defect is an undersized DMA-aligned allocation in the long-HMAC-key normalization path, corrected by allocating the rounded size before copying. The bundle provides several stable-tree commits but no definitive branch-to-fixed-version mapping, exploit evidence, CWE assignment, or proof that every local user can reach the path.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the applicable referenced stable fix.
  • Check distribution or appliance advisories for exact affected and corrected package versions.
  • Restrict unnecessary local access while patching is pending.
  • Review whether CAAM HMAC functionality can be safely disabled if no update is immediately available.

Validation and detection

  • Confirm the running kernel version and distribution package build.
  • Determine whether the CAAM driver is present, enabled, and actively used.
  • Compare kernel source or package metadata with the referenced stable fix commits.
  • Review kernel logs for unexplained memory corruption, crashes, or CAAM-related failures.
  • Test the corrected kernel using authorized oversized-HMAC-key regression coverage.
Prepared
Confidence
medium
Sources
7

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-43044 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-43044Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux199354d7fb6eaa2cc5bb650af0bca624baffee35, 199354d7fb6eaa2cc5bb650af0bca624baffee35, 199354d7fb6eaa2cc5bb650af0bca624baffee35, 199354d7fb6eaa2cc5bb650af0bca624baffee35, 199354d7fb6eaa2cc5bb650af0bca624baffee35unaffected
LinuxLinux6.3, 0, 6.6.134, 6.12.81, 6.18.22, 6.19.12, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.