CVE-2026-98170
Description
A flaw was found in the Linux kernel's SMB client. When processing extended file attributes returned by a server, insufficient buffer validation allows the kernel to read data past the allocated boundaries. A malicious or compromised server could exploit this issue by returning a malformed response, potentially causing a system crash resulting in a Denial of Service (DoS) or disclosing sensitive kernel memory.
Statement
A moderate impact out-of-bounds read flaw was found in the Linux kernel SMB client, affecting the kernel and kernel-rt packages in Red Hat Enterprise Linux 8, 9, and 10, Red Hat In-Vehicle OS 2, and the Red Hat Enterprise Linux CoreOS-based components shipped with OpenShift Container Platform 4. When the SMB client processes extended file attributes returned by a server (for example via getxattr or listxattr), the loop in move_smb2_ea_to_cifs() does not verify that the remaining buffer is large enough to contain a complete smb2_ea_info structure, so reads of the ea_name_length and ea_value_length fields, or of entries reached via an invalid next_entry_offset, can go past the allocated buffer. A malicious or compromised SMB server could return such a malformed response to crash the client kernel (denial of service) or potentially disclose sensitive kernel memory. Red Hat Enterprise Linux 6 and 7 Extended Lifecycle Support are marked not affected because the vulnerable code is not present in those streams. The fix for affected products is currently deferred in line with the moderate severity assessment; exploitation requires a client to connect to an attacker-controlled or compromised SMB server and request extended attributes from it, so the residual risk is limited primarily to kernel crashes or limited information disclosure on systems that mount untrusted SMB shares. Red Hat rates this flaw Moderate with CVSS 3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score 5.5), which is lower than the network-vector severity suggested by some automated upstream scoring, because triggering the issue depends on a local client accessing an untrusted SMB server rather than on an unauthenticated remote attack.
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.