CVE-2024-44946

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-08-31. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

kcm: Serialise kcm_sendmsg() for the same socket.

syzkaller reported UAF in kcm_release(). [0]

The scenario is

  • Thread A builds a skb with MSG_MORE and sets kcm->seq_skb.
  • Thread A resumes building skb from kcm->seq_skb but is blocked
by sk_stream_wait_memory()
  • Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb
and puts the skb to the write queue
  • Thread A faces an error and finally frees skb that is already in the
write queue
  • kcm_release() does double-free the skb in the write queue

When a thread is building a MSG_MORE skb, another thread must not touch it.

Let's add a per-sk mutex and serialise kcm_sendmsg().

[0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge include/linux/skbuff.h:3181 [inline] BUG: KASAN: slab-use-after-free in kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691 Read of size 8 at addr ffff0000ced0fc80 by task syz-executor329/6167

CPU: 1 PID: 6167 Comm: syz-executor329 Tainted: G B 6.8.0-rc5-syzkaller-g9abbc24128bc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:377 [inline] print_report+0x178/0x518 mm/kasan/report.c:488 kasan_report+0xd8/0x138 mm/kasan/report.c:601 __asan_report_load8_noabort+0x20/0x2c mm/kasan/report_generic.c:381 __skb_unlink include/linux/skbuff.h:2366 [inline] __skb_dequeue include/linux/skbuff.h:2385 [inline] __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] __skb_queue_purge include/linux/skbuff.h:3181 [inline] kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691 __sock_release net/socket.c:659 [inline] sock_close+0xa4/0x1e8 net/socket.c:1421 __fput+0x30c/0x738 fs/file_table.c:376 ____fput+0x20/0x30 fs/file_table.c:404 task_work_run+0x230/0x2e0 kernel/task_work.c:180 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x618/0x1f64 kernel/exit.c:871 do_group_exit+0x194/0x22c kernel/exit.c:1020 get_signal+0x1500/0x15ec kernel/signal.c:2893 do_signal+0x23c/0x3b44 arch/arm64/kernel/signal.c:1249 do_notify_resume+0x74/0x1f4 arch/arm64/kernel/entry-common.c:148 exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline] el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:713 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598

Allocated by task 6166: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x40/0x78 mm/kasan/common.c:68 kasan_save_alloc_info+0x70/0x84 mm/kasan/generic.c:626 unpoison_slab_object mm/kasan/common.c:314 [inline] __kasan_slab_alloc+0x74/0x8c 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_node+0x204/0x4c0 mm/slub.c:3903 __alloc_skb+0x19c/0x3d8 net/core/skbuff.c:641 alloc_skb include/linux/skbuff.h:1296 [inline] kcm_sendmsg+0x1d3c/0x2124 net/kcm/kcmsock.c:783 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] sock_sendmsg+0x220/0x2c0 net/socket.c:768 splice_to_socket+0x7cc/0xd58 fs/splice.c:889 do_splice_from fs/splice.c:941 [inline] direct_splice_actor+0xec/0x1d8 fs/splice.c:1164 splice_direct_to_actor+0x438/0xa0c fs/splice.c:1108 do_splice_direct_actor ---truncated---

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
55%
KEV
Not listed

Published

August 31, 2024

Last Modified

August 5, 2026

References (8)

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1054 (5.4.0-1054.58) @ focal2026-05-23ubuntu
ubuntulinux-tools-bluefield (5.4.0.1094.90) @ focal2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1134.143~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.200.196) @ focal2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1038.42) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1072.72) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1075.73) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1119.149) @ focal2026-05-23ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1067.67) @ jammy2026-05-23ubuntu
ubuntulinux-tools-iot (5.4.0.1044.42) @ focal2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1017.18~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure (6.8.0-1020.23) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-05-23ubuntu
linuxKernel @ 4.19.321—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.

Weakness Classification(1)

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

All Vendor Advisories

(17)

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 13× in last 7d / 46× 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 122 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2024-44946?
CVE-2024-44946 is a medium vulnerability published on August 31, 2024. In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSGMORE and sets kcm->seqskb. 2. Thread A resumes building skb from kcm->seq_skb but is…
When was CVE-2024-44946 disclosed?
CVE-2024-44946 was first published in the National Vulnerability Database on August 31, 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-44946 actively exploited?
CVE-2024-44946 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 44.9% of all scored CVEs.
What is the CVSS score of CVE-2024-44946?
CVE-2024-44946 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-44946?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-44946, 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

Explore the affected products and dependency analysis for CVE-2024-44946

Explore →

Is Your Infrastructure Affected by CVE-2024-44946?

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

Start Free Scan →Browse All CVEs