CVE-2026-74567
Description
A flaw was found in the Linux kernel's key management subsystem. An unprivileged local attacker could exploit an out-of-bounds read vulnerability in the keyring_get_key_chunk() function. By providing specially crafted keys, the attacker can cause the system to read beyond its intended memory boundaries. This could lead to the disclosure of sensitive information or a system crash (denial of service).
Statement
A moderate out-of-bounds read flaw was found in the Linux kernel's key management subsystem. When walking description-level key chunks, keyring_get_key_chunk() advances the read pointer past the inline prefix without bounds-checking the full byte offset against the key description length, so a sufficiently long key description can be read past its allocation. A local unprivileged attacker could trigger this flaw through the add_key(2) system call by creating a crafted pair of same-type keys whose index hashes collide, causing a slab out-of-bounds read that could crash the system (denial of service) or disclose a limited amount of kernel memory. The kernel and kernel-rt packages in Red Hat Enterprise Linux 9 and 10 and in Red Hat In-Vehicle OS 2 are affected, and the fix for these streams has been deferred to a future update, so the residual risk is that a local unprivileged user can trigger the out-of-bounds read until a fixed kernel is delivered. The Red Hat Enterprise Linux 6 Extended Lifecycle Support stream is out of support scope, and Red Hat Enterprise Linux 7 and 8 are not affected because the vulnerable code is not present in their kernels. Red Hat rates this flaw as Moderate impact (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), lower than the upstream CVE.org rating of Important (score 7.1), because Red Hat's assessment finds the impact on Red Hat products to be limited to availability with no confidentiality impact.
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).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 7.1 |
| 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 | None | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.