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.
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated client can send many simultaneous SMB requests to Linux’s ksmbd server, consuming excessive kernel memory and potentially causing an out-of-memory outage. The issue affects availability, not data confidentiality or integrity. Exposure is limited to systems running ksmbd, especially where SMB is reachable from untrusted networks.
Executive priority
Treat internet-facing or broadly reachable ksmbd servers as a high-priority availability risk and update promptly. Internal, tightly restricted systems remain important but can follow risk-based scheduling. Business impact may include file-service disruption or complete host instability from memory exhaustion.
Technical view
CVE-2024-50285 is a CWE-770 resource-exhaustion flaw in Linux ksmbd. Existing SMB credit handling did not adequately bound simultaneous outstanding operations, allowing growth of the ksmbd_work_cache until memory exhaustion. The kernel fix rejects work exceeding maximum credits, assuming each SMB request consumes at least one credit.
Likely exposure
Prioritize Linux hosts or appliances running ksmbd with SMB accessible to untrusted clients. Systems not using ksmbd are unlikely to be exposed through this flaw. The supplied affected-version data is ambiguous, so confirm distribution package status and fix backports rather than relying solely on version numbers.
Exploitation context
The CVSS 3.1 score is 7.5: network-accessible, low complexity, no privileges, and no user interaction, with high availability impact. The bundle states KEV is false and provides no evidence of active exploitation or a public exploit. Do not interpret absence from KEV as proof that exploitation is impossible.
Researcher notes
The core invariant introduced by the fix is that outstanding simultaneous SMB work must not exceed maximum credits. Assessment should distinguish ksmbd from other SMB implementations and verify backported commit inclusion. The supplied version list mixes release numbers and commit identifiers, so definitive branch boundaries cannot be established from this bundle alone.
Mitigation direction
Install a vendor-supported kernel update incorporating the referenced ksmbd fixes.
Disable ksmbd where SMB file serving is unnecessary.
Restrict SMB access to trusted networks and clients while updates are pending.
Check Linux distribution advisories for backport and package-specific guidance.
Validation and detection
Identify systems where ksmbd is loaded or SMB services use the in-kernel server.
Record running kernel and distribution package versions on exposed systems.
Confirm the installed kernel contains the applicable referenced fix or vendor backport.
Review monitoring for memory spikes, ksmbd_work_cache growth, and out-of-memory events.
Verify SMB is not exposed beyond intended network boundaries.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.