LiveActive security incident?Get immediate response
CVE Record

CVE-2024-50284: ksmbd: Fix the missing xa_store error check

In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix the missing xa_store error check xa_store() can fail, it return xa_err(-EINVAL) if the entry cannot be stored in an XArray, or xa_err(-ENOMEM) if memory allocation failed, so check error for xa_store() to fix it.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel SMB server component can mishandle an internal storage failure. A remote, unauthenticated actor may be able to disrupt availability on exposed systems, but the sources do not describe a proven attack method. Confidentiality and integrity are not scored as affected. Risk is concentrated in systems that use ksmbd and make it network-reachable.

Executive priority

Address within the normal high-severity patch window, escalating internet-facing or business-critical ksmbd servers. Confirm ksmbd use first because systems not using the component are less likely exposed. The evidence does not support declaring an active exploitation emergency.

Technical view

ksmbd failed to check xa_store() errors. xa_store can return -EINVAL when an entry cannot be stored in an XArray or -ENOMEM on allocation failure. The correction adds error handling. CVSS 3.1 is 7.5: network-accessible, low complexity, no privileges or user interaction, with high availability impact. The issue maps to CWE-754.

Likely exposure

Systems are potentially exposed when running an affected Linux kernel with ksmbd enabled and reachable over a network. Internet-facing or untrusted-network SMB access raises priority. The supplied version records are ambiguous, so confirm applicability against kernel or distribution advisories rather than relying solely on the listed versions.

Exploitation context

The bundle reports no CISA KEV listing, and none of the cited sources establishes active exploitation or a public proof of concept. The CVSS vector indicates a potentially remote, unauthenticated availability attack, but the available evidence does not document practical triggering conditions or real-world incidents.

Researcher notes

The supplied version data is insufficient for deterministic range matching: it mixes versions and commit identifiers across affected and default-unaffected entries. Use the referenced stable commits and distribution advisory to confirm backports. The sources establish missing xa_store error checking but do not document trigger conditions, failure mechanics, proof of concept, or observed exploitation.

Mitigation direction

  • Install a vendor-supported kernel update containing the applicable referenced stable fix or distribution backport.
  • Follow Linux kernel and distribution guidance to resolve ambiguity in the supplied affected-version records.
  • If ksmbd is unnecessary, disable it under normal change-control procedures.
  • Until patched, restrict ksmbd access to trusted networks and clients.
  • Reboot into the updated kernel and confirm the intended version is active.

Validation and detection

  • Inventory running kernel versions on systems providing SMB through ksmbd.
  • Confirm whether ksmbd is enabled and reachable from untrusted or internet-connected networks.
  • Verify the installed kernel contains a referenced fix or an acknowledged distribution backport.
  • Review ksmbd and kernel logs for failures or unexpected service interruptions.
  • After updating, validate SMB availability from an approved client.
Prepared
Confidence
medium
Sources
7

Public sources used

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-754: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-50284 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-50284Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux052b41ef2abe274f068e892aee81406f11bd1f3a, b685757c7b08d5073046fb379be965fd6c06aafc, b685757c7b08d5073046fb379be965fd6c06aafc, b685757c7b08d5073046fb379be965fd6c06aafc, 1f485b54d04a920723984062c912174330a05178, 6.1.71, 5.15.145unaffected
LinuxLinux6.3, 0, 6.1.117, 6.6.61, 6.11.8, 6.12affected
Weakness

CWE details

CWE-754

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-754 · source CWE mapping

Improper Check for Unusual or Exceptional Conditions

Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs