CVE-2024-50285

Description

From CVE.org

In the Linux kernel, the following vulnerability has been resolved: ksmbd: check outstanding simultaneous SMB operations If Client send simultaneous SMB operations to ksmbd, It exhausts too much memory through the "ksmbd_work_cache”. It will cause OOM issue. ksmbd has a credit mechanism but it can't handle this problem. This patch add the check if it exceeds max credits to prevent this problem by assuming that one smb request consumes at least one credit.

Statement

A low severity flaw was found in the Linux kernel's ksmbd in-kernel SMB3 server. A client that sends a large number of simultaneous SMB operations to a host running the ksmbd server can exhaust kernel memory through the ksmbd_work_cache, because ksmbd's credit mechanism does not limit outstanding simultaneous operations, causing an out-of-memory condition that results in a denial of service. Only availability is affected; there is no impact on confidentiality or integrity. Only systems running a kernel that provides and enables the ksmbd SMB server are exposed to this flaw. Red Hat Enterprise Linux 6, 7, 8, and 9, including the kernel and kernel-rt packages, as well as Red Hat's Hosted OpenShift offerings, are not affected because the ksmbd module is not supported and not enabled in those kernels. The only affected Red Hat maintained software is the Fedora community kernel, for which a fix is being pursued by the community through the delegated resolution. The upstream fix adds a check that rejects requests when outstanding simultaneous SMB operations exceed the maximum number of SMB credits, based on the assumption that each SMB request consumes at least one credit. The CVE.org record scores this issue 7.5 (Important) with a network attack vector requiring no privileges, whereas Red Hat scores it 5.5 (Moderate) with a local attack vector and low privileges required, reflecting a conservative assessment of this availability-only memory exhaustion.

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 HatNVDcve.org
Base Score5.55.55.5
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredLowLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneNone
Integrity ImpactNoneNoneNone
Availability ImpactHighHighHigh

Vector

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

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

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

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

When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.

Frequently Asked Questions

Want to get errata notifications? Sign up here.