CVE-2026-74751
Description
A flaw was found in the Linux kernel's RISC-V (Reduced Instruction Set Computer - V) ZBB-optimized strnlen function. This vulnerability occurs because the strnlen loop attempts to read one word beyond the intended boundary. If the read operation crosses an unmapped memory page, it can lead to a system fault, resulting in a denial of service (DoS) for the affected system.
Statement
A moderate-impact flaw was found in the Linux kernel's RISC-V ZBB-optimized strnlen implementation. The optimized strnlen loop loads the next machine word before checking the aligned boundary, so when the input buffer is aligned and the byte count is a multiple of the register size, the loop can read one full word past the end of the supplied count. If that out-of-bounds read lands on a page boundary with the following page unmapped, it faults in kernel context, resulting in a denial of service. Triggering the fault requires a local process able to influence a kernel strnlen call with a specific buffer layout and memory mapping, which is why Red Hat Product Security rates this flaw Moderate (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) with the impact limited to availability. This differs significantly from the CVE.org record, which scores the issue Critical (9.4) with a network attack vector and confidentiality and integrity impacts that the technical evidence does not support. All currently assessed Red Hat Enterprise Linux and Red Hat In-Vehicle OS streams are marked not affected because the vulnerable RISC-V ZBB strnlen code is not present in the shipped kernels for those streams.
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 | 9.4 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | Low |
| 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:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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.