CVE-2024-53124

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.7 from GitHub Security Advisory published 2024-12-02. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-51796 (ENISA EUVD) · GHSA-c7fm-gwfm-q8c7 (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: fix data-races around sk->sk_forward_alloc

Syzkaller reported this warning: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 16 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x1c5/0x1e0 Modules linked in: CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.12.0-rc5 #26 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:inet_sock_destruct+0x1c5/0x1e0 Code: 24 12 4c 89 e2 5b 48 c7 c7 98 ec bb 82 41 5c e9 d1 18 17 ff 4c 89 e6 5b 48 c7 c7 d0 ec bb 82 41 5c e9 bf 18 17 ff 0f 0b eb 83 <0f> 0b eb 97 0f 0b eb 87 0f 0b e9 68 ff ff ff 66 66 2e 0f 1f 84 00 RSP: 0018:ffffc9000008bd90 EFLAGS: 00010206 RAX: 0000000000000300 RBX: ffff88810b172a90 RCX: 0000000000000007 RDX: 0000000000000002 RSI: 0000000000000300 RDI: ffff88810b172a00 RBP: ffff88810b172a00 R08: ffff888104273c00 R09: 0000000000100007 R10: 0000000000020000 R11: 0000000000000006 R12: ffff88810b172a00 R13: 0000000000000004 R14: 0000000000000000 R15: ffff888237c31f78 FS: 0000000000000000(0000) GS:ffff888237c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffc63fecac8 CR3: 000000000342e000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? __warn+0x88/0x130 ? inet_sock_destruct+0x1c5/0x1e0 ? report_bug+0x18e/0x1a0 ? handle_bug+0x53/0x90 ? exc_invalid_op+0x18/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? inet_sock_destruct+0x1c5/0x1e0 __sk_destruct+0x2a/0x200 rcu_do_batch+0x1aa/0x530 ? rcu_do_batch+0x13b/0x530 rcu_core+0x159/0x2f0 handle_softirqs+0xd3/0x2b0 ? __pfx_smpboot_thread_fn+0x10/0x10 run_ksoftirqd+0x25/0x30 smpboot_thread_fn+0xdd/0x1d0 kthread+0xd3/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x34/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 ---[ end trace 0000000000000000 ]---

Its possible that two threads call tcp_v6_do_rcv()/sk_forward_alloc_add() concurrently when sk->sk_state == TCP_LISTEN with sk->sk_lock unlocked, which triggers a data-race around sk->sk_forward_alloc: tcp_v6_rcv tcp_v6_do_rcv skb_clone_and_charge_r sk_rmem_schedule __sk_mem_schedule sk_forward_alloc_add() skb_set_owner_r sk_mem_charge sk_forward_alloc_add() __kfree_skb skb_release_all skb_release_head_state sock_rfree sk_mem_uncharge sk_forward_alloc_add() sk_mem_reclaim // set local var reclaimable __sk_mem_reclaim sk_forward_alloc_add()

In this syzkaller testcase, two threads call tcp_v6_do_rcv() with skb->truesize=768, the sk_forward_alloc changes like this: (cpu 1) | (cpu 2) | sk_forward_alloc ... | ... | 0 __sk_mem_schedule() | | +4096 = 4096 | __sk_mem_schedule() | +4096 = 8192 sk_mem_charge() | | -768 = 7424 | sk_mem_charge() | -768 = 6656 ... | ... | sk_mem_uncharge() | | +768 = 7424 reclaimable=7424 | | | sk_mem_uncharge() | +768 = 8192 | reclaimable=8192 | __sk_mem_reclaim() | | -4096 = 4096 | __sk_mem_reclaim() | -8192 = -4096 != 0

The skb_clone_and_charge_r() should not be called in tcp_v6_do_rcv() when sk->sk_state is TCP_LISTEN, it happens later in tcp_v6_syn_recv_sock(). Fix the same issue in dccp_v6_do_rcv().

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 2, 2024

Last Modified

October 15, 2026

Advisory Details (10)

Auto-updated Jul 19, 2026
Patch available.
Web page

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4075-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4076-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Web page

net: fix data-races around sk->sk_forward_alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe2c0bd6d1e29ccefdc978b9a290571c93c27473
Web page

net: fix data-races around sk->sk_forward_alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d285eb9d0641c8344f2836081b4ccb7b3c5cc1b6
Web page

net: fix data-races around sk->sk_forward_alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3d052cae566ec2285f5999958a5deb415a0f59e
Web page

net: fix data-races around sk->sk_forward_alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be7c61ea5f816168c38955eb4e898adc8b4b32fd
Web page

net: fix data-races around sk->sk_forward_alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/695fb0b9aecfd5dd5b2946ba8897ac2c1eef654d
Web page

net: fix data-races around sk->sk_forward_alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f51f8c9d28954cf380100883a02eed35a8277e9
Web page

net: fix data-races around sk->sk_forward_alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/073d89808c065ac4c672c0a613a71b27a80691cb

Vendor Advisories for CVE-2024-53124(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-09-08ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-09-08ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-09-08ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-09-08ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-09-08ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-09-08ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.136.147~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1018.19) @ noble2026-09-08ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2024.25) @ noble2026-09-08ubuntu
ubuntulinux-tools-raspi (6.8.0-1029.33) @ noble2026-09-08ubuntu
ubuntulinux-tools-gcp-lts-24.04 (6.8.0-1031.33) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1030.35) @ noble2026-09-08ubuntu
ubuntulinux-tools-kvm (4.15.0.1168.159) @ bionic2026-09-08ubuntu
ubuntulinux-tools-azure-fips-4.15 (4.15.0.2104.100) @ bionic2026-09-08ubuntu
ubuntulinux-tools-oracle (4.15.0.1148.159~16.04.1) @ xenial2026-09-08ubuntu
ubuntulinux-tools-fips (4.4.0.1119.120) @ xenial2026-09-08ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.135.133) @ jammy2026-09-08ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-09-08ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-09-08ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-09-08ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-09-08ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-09-08ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.211.206) @ focal2026-09-08ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1060 (5.4.0-1060.64) @ focal2026-09-08ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1145.87) @ focal2026-09-08ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-09-08ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1086.95~20.04.1.61) @ focal2026-09-08ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1077.83~20.04.1) @ focal2026-09-08ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 5.4.290 (fixes >=4.4.0)—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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (34 versions)
  • every version up to 6.1.128-1: fixed in 6.1.128-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.10-1: fixed in 6.11.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.10-1: fixed in 6.11.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(23)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 239 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 144 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-53124?
CVE-2024-53124 is a medium-severity vulnerability; its CVE record was published on December 2, 2024. In the Linux kernel, the following vulnerability has been resolved: net: fix data-races around sk->sk_forward_alloc Syzkaller reported this warning: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 16 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x1c5/0x1e0 Modules linked in: CPU: 0 UID: 0…
When was the CVE record for CVE-2024-53124 published?
The CVE record for CVE-2024-53124 was published on December 2, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-53124 actively exploited?
CVE-2024-53124 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-53124?
CVE-2024-53124 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2024-53124?
A fix for CVE-2024-53124 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-53124 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-53124?

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

Book a Demo →Browse All CVEs