CVE-2026-97560
Description
A flaw was found in the Linux kernel's SMB (Server Message Block) client. When parsing a share-root relative native symbolic link, an incorrect length calculation causes the client to read past the end of the allocated buffer in the smb2_parse_native_symlink function. A malicious server or attacker providing crafted SMB responses can exploit this issue to trigger a Denial of Service (DoS) via a kernel crash or potentially expose sensitive kernel memory.
Statement
A moderate impact flaw was found in the Linux kernel SMB client (fs/smb/client/reparse.c) in smb2_parse_native_symlink(). When parsing a share-root relative native symlink, the code copies from smb_target+1 to skip the leading separator but uses strlen(smb_target)+1 as the length, reading one byte past the allocated buffer. A malicious or compromised SMB server can supply a crafted symlink target (reparse point); when a local user or workload then accesses such a symlink on a mounted SMB share (for example via a stat or path lookup), the out-of-bounds read is triggered, which can crash the kernel and cause a denial of service. Only a single byte past the string terminator is read, and the Red Hat assessment found no evidence of information disclosure, so the impact is limited to availability (Red Hat CVSS 3.1: 5.5, MODERATE, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), despite the CVE description mentioning possible exposure of sensitive kernel memory. The vulnerable code was introduced into Red Hat kernels through a backport of the 'cifs: Fix parsing native symlinks relative to the export' change and is present only in newer streams; Red Hat Enterprise Linux 6, 7, and 8, the RHEL 9.2 and 9.4 update streams and their kernel-rt builds, and OpenShift Container Platform 4.12 through 4.18 are not affected because the vulnerable code is not present there. For the affected streams (Red Hat Enterprise Linux 9 versions 9.6 and later, Red Hat Enterprise Linux 10, Red Hat In-Vehicle OS 2, and OpenShift Container Platform 4.19 and later), the fix is deferred: this one-byte out-of-bounds read has a practical consequence of a local denial of service rather than memory corruption or privilege escalation, so it does not warrant an immediate out-of-cycle update and the fix will be delivered in a future scheduled kernel update. The residual risk is a kernel crash on systems where a user accesses a crafted native symlink on an SMB share served by a malicious server.
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 | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.