CVE-2026-43330
Description
A flaw was found in the Linux kernel's caam cryptographic accelerator driver. When processing a Hash-based Message Authentication Code (HMAC) key that exceeds the block size, the driver incorrectly handles memory allocation and copying. This can lead to an overflow, where the system attempts to read beyond the intended memory buffer, potentially corrupting neighboring memory. This memory corruption could lead to system instability or denial of service.
Statement
A moderate-severity out-of-bounds read flaw was found in the Linux kernel's CAAM (Cryptographic Accelerator and Assurance Module) driver. When an HMAC key longer than the hash block size is set, the driver copies the key into a buffer sized to the DMA cache alignment using kmemdup, which reads (aligned_len - keylen) bytes beyond the end of the keylen-sized source buffer. The over-read data is hashed back into the real key, which can expose adjacent kernel memory and corrupt neighbouring memory, resulting in system instability or denial of service. Exploitation requires local access to a system equipped with the CAAM cryptographic accelerator whose algorithms are in use, so a local process able to reach the kernel crypto setkey path can trigger the flaw. This flaw affects the kernel in Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2, where fixes are being pursued through the respective delegated maintenance streams. Earlier Red Hat Enterprise Linux versions (RHEL 6, 7, 8, and 9, including kernel-rt) are not affected because the vulnerable code is not present in those kernels. Although the upstream CVSS 3.1 score is 7.8 (IMPORTANT), Red Hat rates this flaw as MODERATE because it is not network reachable, requires local access on hardware with the CAAM accelerator, and the primary impact is denial of service.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.1 | N/A | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.