Security readout for executives and security teams
Plain-English summary
A Linux kernel socket-creation error can leave an invalid pointer behind when AF_SMC setup fails. A locally authenticated attacker may potentially exploit this memory-safety flaw to compromise confidentiality, integrity, or availability. The supplied evidence rates it high severity but does not establish real-world exploitation.
Executive priority
Treat this as a high-priority kernel update for affected systems permitting untrusted local code or multiple users. It is less urgent than an unauthenticated remote flaw, and active exploitation is not established. Require prompt inventory, vendor confirmation, controlled rollout, and reboot verification.
Technical view
CVE-2024-50293 is a CWE-416 use-after-free condition in __smc_create(). On an AF_SMC creation failure, sock->sk may remain dangling instead of being cleared. Syzbot discovered the defect through a kernel warning. The CVSS 3.1 score is 7.8, requiring local access and low privileges without user interaction.
Likely exposure
Exposure is limited to affected Linux kernels where an attacker can execute locally and reach AF_SMC socket creation. The bundle identifies Linux 6.11 through 6.11.8 and 6.12 as affected. It does not identify distributions, configurations, containers, or appliances that expose the vulnerable path.
Exploitation context
The CVSS vector indicates local, low-privileged exploitation with low complexity and no user interaction. Potential impact is high across confidentiality, integrity, and availability. KEV is false, and the supplied sources provide no evidence of active exploitation or a public weaponized exploit.
Researcher notes
The evidence documents a dangling sock->sk pointer on the AF_SMC failure path and links two stable-kernel corrections. Syzbot reproduced a warning, but the bundle does not describe successful privilege escalation, exploitation reliability, required configuration, or exact fixed release mapping. Avoid inferring those details without additional vendor evidence.
Mitigation direction
- Obtain a vendor-supported kernel containing the referenced AF_SMC correction or its downstream equivalent.
- Prioritize affected multi-user systems and hosts running untrusted local workloads.
- Consult Linux distribution or appliance vendor guidance for corrected package versions.
- Use existing access controls to reduce untrusted local execution until updates are applied.
Validation and detection
- Record each system's running kernel version and compare it with the affected versions.
- Confirm the installed kernel includes a referenced stable correction or documented downstream equivalent.
- Reboot updated systems and verify the corrected kernel is actively running.
- Review vendor advisories because package versions may not match upstream kernel numbering.
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-50293 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
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.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
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/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/d2cc492124e1f22daa1700f069bcc58788043381CVE reference, Linux
- https://git.kernel.org/stable/c/d293958a8595ba566fb90b99da4d6263e14fee15CVE reference, Linux
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.