CVE-2026-99322

Description

A flaw was found in the Linux kernel's Server Message Block (SMB) file server, ksmbd. When handling replayed file creation requests across communication channels while an original channel is closing, ksmbd fails to properly update connection and lock references to the active channel. A remote attacker could exploit this flaw to trigger improper reference counting and access stale state, potentially leading to memory corruption or a denial of service (DoS) via a system crash.

Statement

This vulnerability is rated as having a Moderate severity for Red Hat because exploitation requires valid user credentials and is confined to causing a denial of service without compromising system confidentiality or integrity. In standard Red Hat Enterprise Linux deployments, the in-kernel ksmbd server is not loaded by default, as production environments typically deploy the user-space Samba suite for SMB networking. Systems are only exposed if ksmbd is manually configured and running, where an authenticated network client can trigger inconsistent reference counts during multichannel request replay.

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)

Availability

Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing an error that causes the product to crash or exit out of its current operation.

Frequently Asked Questions

Want to get errata notifications? Sign up here.