Security readout for executives and security teams
Plain-English summary
A memory safety flaw in Linux’s ksmbd SMB server can let a user session be freed while it is still needed. The supplied CVSS assessment rates potential confidentiality, integrity, and availability impact as high, without authentication or user interaction. Actual exploit outcomes are not demonstrated in the supplied evidence.
Executive priority
Prioritize rapid inventory and remediation for network-reachable ksmbd servers. The technical severity is critical, but urgency should be highest where affected kernels actually run ksmbd and accept untrusted connections. No active exploitation evidence is provided, so communicate this as high potential impact rather than a confirmed ongoing campaign.
Technical view
CVE-2024-50283 is a CWE-416 slab use-after-free in smb3_preauth_hash_rsp. The session can be released before the response preauthentication hash operation uses it. The kernel fix moves ksmbd_user_session_put under smb3_preauth_hash_rsp so the session remains valid during processing. CVSS 3.1 is 9.8: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Likely exposure
Exposure requires Linux systems using ksmbd on an affected kernel, with risk increasing when SMB is network-reachable. The bundle lists affected releases including 5.15, 5.15.174, 6.1.117, 6.6.61, 6.11.8, and 6.12. Distribution-specific backports may alter exposure, so version strings alone are insufficient.
Exploitation context
The CVSS vector describes a network-accessible, low-complexity, unauthenticated condition requiring no user interaction. However, the bundle marks the CVE as absent from KEV and supplies no evidence of active exploitation or a public working exploit. Treat the vector as potential exploitability, not proof that exploitation is occurring.
Researcher notes
The central issue is session lifetime ordering around SMB3 preauthentication response hashing. Review the referenced stable commits and distribution backports rather than relying solely on upstream version numbers. The source bundle contains repeated commit identifiers and an unusual affected-version entry of “0”; these data-quality limitations warrant vendor-specific confirmation.
Mitigation direction
- Identify systems running ksmbd and record their kernel and distribution package versions.
- Apply vendor-supported kernels containing the referenced stable fix or an equivalent distribution backport.
- Check Linux and distribution advisories for exact fixed package versions.
- Until patched, reduce untrusted network access to ksmbd where operationally feasible.
Validation and detection
- Confirm whether ksmbd is enabled or loaded on each potentially affected system.
- Compare installed kernel packages against vendor advisories and backport notices.
- Verify the installed kernel contains the relevant stable fix or equivalent patch.
- After updating, confirm systems booted into the corrected kernel.
- Monitor ksmbd hosts for abnormal crashes while recognizing crashes alone do not prove exploitation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-416: 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 lookupCVE-2024-50283 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/cb645064e0811053c94e86677f2e58ed29359d62CVE reference, Linux
- https://git.kernel.org/stable/c/f7557bbca40d4ca8bb1c6c940ac6c95078bd0827CVE reference, Linux
- https://git.kernel.org/stable/c/c6cdc08c25a868a08068dfc319fa9fce982b8e7fCVE reference, Linux
- https://git.kernel.org/stable/c/1b6ad475d4ed577d34e0157eb507be00c588bf5cCVE reference, Linux
- https://git.kernel.org/stable/c/b8fc56fbca7482c1e5c0e3351c6ae78982e25adaCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.