CVE-2026-97565
Description
A flaw was found in the Linux kernel's SMB (Server Message Block) client. When communicating with a malicious or compromised server, the client fails to verify that an incoming read response meets the expected minimum header size before accessing header fields. A malicious server can send a truncated response packet, triggering an out-of-bounds memory read during header parsing. This flaw primarily leads to a system crash, resulting in a Denial of Service (DoS), or potential information disclosure.
Statement
A moderate out-of-bounds read flaw was found in the Linux kernel CIFS/SMB client in CIFSSMBRead(). The client reads the DataLengthHigh, DataLength and DataOffset fields of an SMB1 READ response without first verifying that the response is at least as large as the READ_RSP header. A malicious or compromised SMB server can return a truncated response, causing the client to read past the end of the receive buffer, which can crash the kernel (denial of service) or potentially disclose kernel memory. This flaw affects the kernel and kernel-rt packages in Red Hat Enterprise Linux 8, 9 and 10, the kernel packages in Red Hat In-Vehicle OS, and the RHEL CoreOS images shipped with OpenShift Container Platform. Red Hat Enterprise Linux 6 and 7 are not affected because the vulnerable code is not present in those releases. Exploitation requires explicit configuration: SMB1 is not negotiated by default, so the vulnerable path is reached only when a client mounts a share with the legacy vers=1.0 option against a malicious or compromised server. Because of the moderate severity and the non-default configuration needed to reach the vulnerable code, the fix is currently deferred for the affected products and will be addressed in a future update; until then, the residual risk is a kernel crash or potential information disclosure on systems that use vers=1.0 CIFS mounts against untrusted servers. Red Hat rated this flaw Moderate severity with a CVSS 3.1 base score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
Mitigation
The vulnerable code path is reachable only through the legacy SMB1 protocol, which the kernel CIFS client does not negotiate by default. Avoid mounting CIFS shares with the vers=1.0 option, including entries in /etc/fstab or autofs maps; rely on the default protocol negotiation or explicitly request a newer dialect such as vers=2.1 or vers=3.0, and remount any existing SMB1 mounts using a newer dialect. Additionally, restricting CIFS mounts to trusted, non-compromised SMB servers reduces exposure to a malicious server returning truncated responses.
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.