CVE-2024-26625

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-03-06. 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:

llc: call sock_orphan() at release time

syzbot reported an interesting trace [1] caused by a stale sk->sk_wq pointer in a closed llc socket.

In commit ff7b11aa481f ("net: socket: set sock->sk to NULL after calling proto_ops::release()") Eric Biggers hinted that some protocols are missing a sock_orphan(), we need to perform a full audit.

In net-next, I plan to clear sock->sk from sock_orphan() and amend Eric patch to add a warning.

[1] BUG: KASAN: slab-use-after-free in list_empty include/linux/list.h:373 [inline] BUG: KASAN: slab-use-after-free in waitqueue_active include/linux/wait.h:127 [inline] BUG: KASAN: slab-use-after-free in sock_def_write_space_wfree net/core/sock.c:3384 [inline] BUG: KASAN: slab-use-after-free in sock_wfree+0x9a8/0x9d0 net/core/sock.c:2468 Read of size 8 at addr ffff88802f4fc880 by task ksoftirqd/1/27

CPU: 1 PID: 27 Comm: ksoftirqd/1 Not tainted 6.8.0-rc1-syzkaller-00049-g6098d87eaf31 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc4/0x620 mm/kasan/report.c:488 kasan_report+0xda/0x110 mm/kasan/report.c:601 list_empty include/linux/list.h:373 [inline] waitqueue_active include/linux/wait.h:127 [inline] sock_def_write_space_wfree net/core/sock.c:3384 [inline] sock_wfree+0x9a8/0x9d0 net/core/sock.c:2468 skb_release_head_state+0xa3/0x2b0 net/core/skbuff.c:1080 skb_release_all net/core/skbuff.c:1092 [inline] napi_consume_skb+0x119/0x2b0 net/core/skbuff.c:1404 e1000_unmap_and_free_tx_resource+0x144/0x200 drivers/net/ethernet/intel/e1000/e1000_main.c:1970 e1000_clean_tx_irq drivers/net/ethernet/intel/e1000/e1000_main.c:3860 [inline] e1000_clean+0x4a1/0x26e0 drivers/net/ethernet/intel/e1000/e1000_main.c:3801 __napi_poll.constprop.0+0xb4/0x540 net/core/dev.c:6576 napi_poll net/core/dev.c:6645 [inline] net_rx_action+0x956/0xe90 net/core/dev.c:6778 __do_softirq+0x21a/0x8de kernel/softirq.c:553 run_ksoftirqd kernel/softirq.c:921 [inline] run_ksoftirqd+0x31/0x60 kernel/softirq.c:913 smpboot_thread_fn+0x660/0xa10 kernel/smpboot.c:164 kthread+0x2c6/0x3a0 kernel/kthread.c:388 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

Allocated by task 5167: kasan_save_stack+0x33/0x50 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:314 [inline] __kasan_slab_alloc+0x81/0x90 mm/kasan/common.c:340 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slub.c:3813 [inline] slab_alloc_node mm/slub.c:3860 [inline] kmem_cache_alloc_lru+0x142/0x6f0 mm/slub.c:3879 alloc_inode_sb include/linux/fs.h:3019 [inline] sock_alloc_inode+0x25/0x1c0 net/socket.c:308 alloc_inode+0x5d/0x220 fs/inode.c:260 new_inode_pseudo+0x16/0x80 fs/inode.c:1005 sock_alloc+0x40/0x270 net/socket.c:634 __sock_create+0xbc/0x800 net/socket.c:1535 sock_create net/socket.c:1622 [inline] __sys_socket_create net/socket.c:1659 [inline] __sys_socket+0x14c/0x260 net/socket.c:1706 __do_sys_socket net/socket.c:1720 [inline] __se_sys_socket net/socket.c:1718 [inline] __x64_sys_socket+0x72/0xb0 net/socket.c:1718 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd3/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b

Freed by task 0: kasan_save_stack+0x33/0x50 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3f/0x60 mm/kasan/generic.c:640 poison_slab_object mm/kasan/common.c:241 [inline] __kasan_slab_free+0x121/0x1b0 mm/kasan/common.c:257 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2121 [inlin ---truncated---

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
17%
KEV
Not listed

Published

March 6, 2024

Last Modified

August 5, 2026

Advisory Details (8)

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

llc: call sock_orphan() at release time - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/64babb17e8150771c58575d8f93a35c5296b499f
generic

llc: call sock_orphan() at release time - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3151051b787f7cd7e3329ea0016eb9113c248812
generic

llc: call sock_orphan() at release time - kernel/git/stable/linux.git - Linux kernel stable tree

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

llc: call sock_orphan() at release time - kernel/git/stable/linux.git - Linux kernel stable tree

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

llc: call sock_orphan() at release time - kernel/git/stable/linux.git - Linux kernel stable tree

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

llc: call sock_orphan() at release time - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c333d9891f34cea8af1b229dc754552304c8eee
generic

llc: call sock_orphan() at release time - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8e51f084b5716653f19e291ed5f026791d4b3ed4
generic

llc: call sock_orphan() at release time - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b950c712a9a05cdda4aea7fcb2848766576c11b

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.106.106) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oem-22.04c (6.1.0.1035.36) @ jammy2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1043 (5.4.0-1043.47) @ focal2026-05-24ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1057.57) @ jammy2026-05-24ubuntu
ubuntulinux-tools-bluefield (5.4.0.1084.80) @ focal2026-05-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.41.41) @ mantic2026-05-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1054.52) @ jammy2026-05-24ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1061.61) @ jammy2026-05-24ubuntu
ubuntulinux-tools-starfive (6.5.0.1015.17) @ mantic2026-05-24ubuntu
ubuntulinux-tools-laptop-23.10 (6.5.0.1017.20) @ mantic2026-05-24ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1058.64~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.26) @ mantic2026-05-24ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1024.26) @ jammy2026-05-24ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.5.0.1021.29) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.41.41~22.04.2) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.262.268) @ xenial2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.24~22.04.1) @ jammy2026-05-24ubuntu
ubuntulinux-tools-kvm (4.4.0.1140.137) @ xenial2026-05-24ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.232.244~16.04.1) @ xenial2026-05-24ubuntu
ubuntulinux-tools-azure-edge (4.15.0.1184.199~16.04.1) @ xenial2026-05-24ubuntu
linuxKernel @ 4.19.307osv

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

(6 across 5 ecosystems)
Debian:10(2)
PackageVulnerable rangeFixed inDependents
linux4.19.118-1 ... 4.19.98-1~bpo9+1 (46 versions)4.19.316-1
linux-5.105.10.136-1~deb10u1 ... 5.10.209-2~deb10u1 (13 versions)5.10.216-1~deb10u1
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)5.10.216-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (18 versions)6.1.82-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.7.7-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.7.7-1

Weakness Classification(1)

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

All Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 4× in last 7d / 24× 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 170 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-26625?
CVE-2024-26625 is a high vulnerability published on March 6, 2024. In the Linux kernel, the following vulnerability has been resolved: llc: call sock_orphan() at release time syzbot reported an interesting trace [1] caused by a stale sk->sk_wq pointer in a closed llc socket. In commit ff7b11aa481f ("net: socket: set sock->sk to NULL after calling…
When was CVE-2024-26625 disclosed?
CVE-2024-26625 was first published in the National Vulnerability Database on March 6, 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-26625 actively exploited?
CVE-2024-26625 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 83.5% of all scored CVEs.
What is the CVSS score of CVE-2024-26625?
CVE-2024-26625 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-26625?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-26625, 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-26625

Explore →

Is Your Infrastructure Affected by CVE-2024-26625?

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