CVE-2026-99385

Description

A flaw was found in the Linux kernel's Server Message Block (SMB) client. A local user can exploit this vulnerability to cause a Denial of Service (DoS) or memory corruption by supplying an oversized Universal Naming Convention (UNC) mount path. Because the client allocates a fixed-size memory buffer without validating the path length, processing an excessively long path leads to a heap buffer overflow that writes beyond the allocated memory.

Statement

This flaw is rated as Moderate severity because exploitation requires local administrative or mount capabilities to specify oversized UNC mount options, limiting the blast radius to a privileged denial of service. On standard Red Hat Enterprise Linux installations, mounting SMB shares requires elevated privileges such as CAP_SYS_ADMIN, preventing unprivileged users from directly corrupting kernel memory. Consequently, systems that do not delegate mount privileges to untrusted local users face minimal risk.

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 Score4.4N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.