CVE-2026-99387

Description

A flaw was found in the Linux kernel's Server Message Block (SMB) client. A malicious SMB server can trigger an out-of-bounds memory read leading to information disclosure by providing a specially crafted response during file lock operations. Because the client does not properly validate server-supplied offsets against the response buffer length, an attacker can cause the system to read beyond the buffer and expose sensitive kernel memory to local user applications.

Statement

This vulnerability is rated as Important because a malicious SMB server can trigger an out-of-bounds memory read, potentially exposing sensitive kernel memory to local user processes or causing a client denial of service. In standard Red Hat Enterprise Linux deployments, SMB connections negotiate modern SMB3 dialects by default, whereas this issue resides exclusively in legacy SMB 1.0 POSIX file locking operations. Consequently, exploitation requires a host to actively establish legacy CIFS mounts to untrusted or compromised remote file shares.

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 HatNVDcve.org
Base Score7.1N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionRequiredN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityLowN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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

Want to get errata notifications? Sign up here.