CVE-2024-50293

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-11-19. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/smc: do not leave a dangling sk pointer in __smc_create()

Thanks to commit 4bbd360a5084 ("socket: Print pf->create() when it does not clear sock->sk on failure."), syzbot found an issue with AF_SMC:

smc_create must clear sock->sk on failure, family: 43, type: 1, protocol: 0 WARNING: CPU: 0 PID: 5827 at net/socket.c:1565 __sock_create+0x96f/0xa30 net/socket.c:1563 Modules linked in: CPU: 0 UID: 0 PID: 5827 Comm: syz-executor259 Not tainted 6.12.0-rc6-next-20241106-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 RIP: 0010:__sock_create+0x96f/0xa30 net/socket.c:1563 Code: 03 00 74 08 4c 89 e7 e8 4f 3b 85 f8 49 8b 34 24 48 c7 c7 40 89 0c 8d 8b 54 24 04 8b 4c 24 0c 44 8b 44 24 08 e8 32 78 db f7 90 <0f> 0b 90 90 e9 d3 fd ff ff 89 e9 80 e1 07 fe c1 38 c1 0f 8c ee f7 RSP: 0018:ffffc90003e4fda0 EFLAGS: 00010246 RAX: 099c6f938c7f4700 RBX: 1ffffffff1a595fd RCX: ffff888034823c00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 00000000ffffffe9 R08: ffffffff81567052 R09: 1ffff920007c9f50 R10: dffffc0000000000 R11: fffff520007c9f51 R12: ffffffff8d2cafe8 R13: 1ffffffff1a595fe R14: ffffffff9a789c40 R15: ffff8880764298c0 FS: 000055557b518380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fa62ff43225 CR3: 0000000031628000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: sock_create net/socket.c:1616 [inline] __sys_socket_create net/socket.c:1653 [inline] __sys_socket+0x150/0x3c0 net/socket.c:1700 __do_sys_socket net/socket.c:1714 [inline] __se_sys_socket net/socket.c:1712 [inline]

For reference, see commit 2d859aff775d ("Merge branch 'do-not-leave-dangling-sk-pointers-in-pf-create-functions'")

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

November 19, 2024

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

net/smc: do not leave a dangling sk pointer in __smc_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d293958a8595ba566fb90b99da4d6263e14fee15
generic

net/smc: do not leave a dangling sk pointer in __smc_create() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2cc492124e1f22daa1700f069bcc58788043381

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
linuxKernel @ 6.11.8—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.9-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.9-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 174 total refreshes for this CVE.

  1. 2026-09-20 20:14 UTCEPSS rescore
  2. 2026-09-20 20:14 UTCEPSS rescore
  3. 2026-09-19 15:40 UTCEPSS rescore
  4. 2026-09-18 19:26 UTCEPSS rescore
  5. 2026-09-17 19:27 UTCEPSS rescore
  6. 2026-09-16 14:06 UTCEPSS rescore
  7. 2026-09-16 05:12 UTCEPSS rescore
  8. 2026-09-15 03:08 UTCEPSS rescore
  9. 2026-09-15 03:08 UTCEPSS rescore
  10. 2026-09-13 16:45 UTCEPSS rescore
  11. 2026-09-12 14:59 UTCEPSS rescore
  12. 2026-09-11 14:51 UTCEPSS rescore
  13. 2026-09-11 09:35 UTCEPSS rescore
  14. 2026-09-10 09:33 UTCEPSS rescore
  15. 2026-09-08 21:58 UTCEPSS rescore
  16. 2026-09-07 16:00 UTCEPSS rescore
  17. 2026-09-07 08:18 UTCOSV refresh
  18. 2026-09-06 13:46 UTCEPSS rescore
  19. 2026-09-06 13:46 UTCEPSS rescore
  20. 2026-09-04 13:59 UTCEPSS rescore
  21. 2026-09-04 05:05 UTCEPSS rescore
  22. 2026-09-02 14:10 UTCEPSS rescore
  23. 2026-09-01 13:52 UTCEPSS rescore
  24. 2026-09-01 13:52 UTCEPSS rescore
  25. 2026-09-01 04:37 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 19:16 UTCEPSS rescore
  2. 2026-08-30 01:20 UTCEPSS rescore
  3. 2026-08-28 21:39 UTCEPSS rescore
  4. 2026-08-26 14:44 UTCEPSS rescore
  5. 2026-08-25 13:47 UTCEPSS rescore
  6. 2026-08-24 14:15 UTCEPSS rescore
  7. 2026-08-23 00:18 UTCEPSS rescore
  8. 2026-08-21 23:47 UTCEPSS rescore
  9. 2026-08-20 22:54 UTCEPSS rescore
  10. 2026-08-20 18:01 UTCOSV refresh
  11. 2026-08-19 17:02 UTCEPSS rescore
  12. 2026-08-19 17:02 UTCEPSS rescore
  13. 2026-08-18 13:46 UTCEPSS rescore
  14. 2026-08-17 13:45 UTCEPSS rescore
  15. 2026-08-16 14:54 UTCEPSS rescore
  16. 2026-08-16 02:13 UTCEPSS rescore
  17. 2026-08-15 01:29 UTCEPSS rescore
  18. 2026-08-13 21:59 UTCEPSS rescore
  19. 2026-08-12 13:49 UTCEPSS rescore
  20. 2026-08-11 13:40 UTCEPSS rescore
  21. 2026-08-10 23:58 UTCEPSS rescore
  22. 2026-08-09 13:45 UTCEPSS rescore
  23. 2026-08-08 16:35 UTCEPSS rescore
  24. 2026-08-07 16:25 UTCEPSS rescore
  25. 2026-08-06 13:45 UTCEPSS rescore
  26. 2026-08-05 19:16 UTCEPSS rescore
  27. 2026-08-05 11:53 UTCEG score recompute
  28. 2026-08-05 11:53 UTCVendor advisory
  29. 2026-08-05 11:53 UTCGHSA enrichment
  30. 2026-08-04 15:08 UTCEPSS rescore
  31. 2026-08-04 11:23 UTCEG score recompute
  32. 2026-08-04 11:23 UTCGHSA enrichment
  33. 2026-08-04 10:36 UTCEPSS rescore
  34. 2026-08-03 10:34 UTCEPSS rescore
  35. 2026-08-02 02:25 UTCEPSS rescore
  36. 2026-08-01 04:14 UTCEPSS rescore
  37. 2026-08-01 04:14 UTCEPSS rescore
  38. 2026-07-31 07:12 UTCOSV refresh
  39. 2026-07-30 16:26 UTCEPSS rescore
  40. 2026-07-30 01:29 UTCEPSS rescore
  41. 2026-07-28 15:35 UTCEPSS rescore
  42. 2026-07-27 14:11 UTCEPSS rescore
  43. 2026-07-26 14:53 UTCEPSS rescore
  44. 2026-07-26 14:53 UTCEPSS rescore
  45. 2026-07-25 14:17 UTCEPSS rescore
  46. 2026-07-25 14:16 UTCEPSS rescore
  47. 2026-07-24 14:16 UTCEPSS rescore
  48. 2026-07-23 14:17 UTCEPSS rescore
  49. 2026-07-23 14:17 UTCEPSS rescore
  50. 2026-07-23 02:42 UTCEG score recompute
  51. 2026-07-22 14:07 UTCEPSS rescore
  52. 2026-07-22 14:07 UTCEPSS rescore
  53. 2026-07-21 15:23 UTCEPSS rescore
  54. 2026-07-20 17:06 UTCEPSS rescore
  55. 2026-07-19 14:30 UTCEPSS rescore
  56. 2026-07-19 14:30 UTCEPSS rescore
  57. 2026-07-19 02:28 UTCEPSS rescore
  58. 2026-07-19 02:28 UTCEPSS rescore
  59. 2026-07-18 10:03 UTCEPSS rescore
  60. 2026-07-18 10:03 UTCEPSS rescore
  61. 2026-07-16 17:02 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 16:56 UTCEPSS rescore
  64. 2026-07-15 01:59 UTCEPSS rescore
  65. 2026-07-15 01:59 UTCEPSS rescore
  66. 2026-07-13 22:29 UTCEPSS rescore
  67. 2026-07-13 14:38 UTCOSV refresh
  68. 2026-07-13 06:12 UTCEPSS rescore
  69. 2026-07-12 05:45 UTCEPSS rescore
  70. 2026-07-12 05:45 UTCEPSS rescore
  71. 2026-07-11 08:26 UTCEPSS rescore
  72. 2026-07-09 19:09 UTCEPSS rescore
  73. 2026-07-09 19:09 UTCEPSS rescore
  74. 2026-07-08 15:14 UTCEPSS rescore
  75. 2026-07-07 13:45 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-50293?
CVE-2024-50293 is a high vulnerability published on November 19, 2024. In the Linux kernel, the following vulnerability has been resolved: net/smc: do not leave a dangling sk pointer in smc_create() Thanks to commit 4bbd360a5084 ("socket: Print pf->create() when it does not clear sock->sk on failure."), syzbot found an issue with AF_SMC: smc_create must clear sock->sk…
When was CVE-2024-50293 disclosed?
CVE-2024-50293 was first published in the National Vulnerability Database on November 19, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-50293 actively exploited?
CVE-2024-50293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.2% of all scored CVEs.
What is the CVSS score of CVE-2024-50293?
CVE-2024-50293 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-50293?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-50293, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-50293

Explore →

Is Your Infrastructure Affected by CVE-2024-50293?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs