CVE-2026-99289

Description

A flaw was found in the Linux kernel's ksmbd Server Message Block (SMB) server. This flaw allows a remote attacker to cause a Denial of Service (DoS) or potentially corrupt memory through a use-after-free condition. The issue occurs during session teardown because non-durable open file handles are not properly detached before the session memory is freed. A remote attacker can exploit this flaw by superseding an existing open file instance at the same time the session is destroyed, causing the kernel to access freed memory.

Statement

This vulnerability is rated as Moderate because although it can be triggered over the network, successful exploitation requires authenticated access to an active SMB session and primarily results in a denial of service via a kernel crash rather than arbitrary code execution. The in-kernel SMB server (ksmbd) is not enabled or running by default in Red Hat Enterprise Linux, where file-sharing environments typically rely on user-space Samba implementations. Consequently, systems are only exposed if administrators have explicitly deployed and configured the ksmbd service.

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 Score6.5N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/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:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.