CVE-2024-50154

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-45151 (ENISA EUVD) · GHSA-r9cc-7xcq-fpxg (GitHub Security Advisories)Source: ENISA EUVD

7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink().

Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler().

""" We are seeing a use-after-free from a bpf prog attached to trace_tcp_retransmit_synack. The program passes the req->sk to the bpf_sk_storage_get_tracing kernel helper which does check for null before using it. """

The commit 83fccfc3940c ("inet: fix potential deadlock in reqsk_queue_unlink()") added timer_pending() in reqsk_queue_unlink() not to call del_timer_sync() from reqsk_timer_handler(), but it introduced a small race window.

Before the timer is called, expire_timers() calls detach_timer(timer, true) to clear timer->entry.pprev and marks it as not pending.

If reqsk_queue_unlink() checks timer_pending() just after expire_timers() calls detach_timer(), TCP will miss del_timer_sync(); the reqsk timer will continue running and send multiple SYN+ACKs until it expires.

The reported UAF could happen if req->sk is close()d earlier than the timer expiration, which is 63s by default.

The scenario would be

  • inet_csk_complete_hashdance() calls inet_csk_reqsk_queue_drop(),
but del_timer_sync() is missed
  • reqsk timer is executed and scheduled again
  • req->sk is accept()ed and reqsk_put() decrements rsk_refcnt, but
reqsk timer still has another one, and inet_csk_accept() does not clear req->sk for non-TFO sockets
  • sk is close()d
  • reqsk timer is executed again, and BPF touches req->sk

Let's not use timer_pending() by passing the caller context to __inet_csk_reqsk_queue_drop().

Note that reqsk timer is pinned, so the issue does not happen in most use cases. [1]

[0] BUG: KFENCE: use-after-free read in bpf_sk_storage_get_tracing+0x2e/0x1b0

Use-after-free read at 0x00000000a891fb3a (in kfence-#1): bpf_sk_storage_get_tracing+0x2e/0x1b0 bpf_prog_5ea3e95db6da0438_tcp_retransmit_synack+0x1d20/0x1dda bpf_trace_run2+0x4c/0xc0 tcp_rtx_synack+0xf9/0x100 reqsk_timer_handler+0xda/0x3d0 run_timer_softirq+0x292/0x8a0 irq_exit_rcu+0xf5/0x320 sysvec_apic_timer_interrupt+0x6d/0x80 asm_sysvec_apic_timer_interrupt+0x16/0x20 intel_idle_irq+0x5a/0xa0 cpuidle_enter_state+0x94/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb

kfence-#1: 0x00000000a72cc7b6-0x00000000d97616d9, size=2376, cache=TCPv6

allocated by task 0 on cpu 9 at 260507.901592s: sk_prot_alloc+0x35/0x140 sk_clone_lock+0x1f/0x3f0 inet_csk_clone_lock+0x15/0x160 tcp_create_openreq_child+0x1f/0x410 tcp_v6_syn_recv_sock+0x1da/0x700 tcp_check_req+0x1fb/0x510 tcp_v6_rcv+0x98b/0x1420 ipv6_list_rcv+0x2258/0x26e0 napi_complete_done+0x5b1/0x2990 mlx5e_napi_poll+0x2ae/0x8d0 net_rx_action+0x13e/0x590 irq_exit_rcu+0xf5/0x320 common_interrupt+0x80/0x90 asm_common_interrupt+0x22/0x40 cpuidle_enter_state+0xfb/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb

freed by task 0 on cpu 9 at 260507.927527s: rcu_core_si+0x4ff/0xf10 irq_exit_rcu+0xf5/0x320 sysvec_apic_timer_interrupt+0x6d/0x80 asm_sysvec_apic_timer_interrupt+0x16/0x20 cpuidle_enter_state+0xfb/0x273 cpu_startup_entry+0x15e/0x260 start_secondary+0x8a/0x90 secondary_startup_64_no_verify+0xfa/0xfb

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 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 SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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
46th
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 (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-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-27). 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

November 7, 2024

Last Modified

August 5, 2026

Advisory Details (7)

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

tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51e34db64f4e43c7b055ccf881b7f3e0c31bb26d
Web page

tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/997ae8da14f1639ce6fb66a063dab54031cd61b3
Web page

tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5071beb59ee416e8ab456ac8647a4dabcda823b1
Web page

tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8459d61fbf24967839a70235165673148c7c7f17
Web page

tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/106e457953315e476b3642ef24be25ed862aaba3

Vendor Advisories for CVE-2024-50154(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-raspi-nolpae (5.15.0.1072.70) @ jammy2026-10-27ubuntu
ubuntulinux-tools-ibm (5.15.0.1070.66) @ jammy2026-10-27ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1075.81~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.133.132) @ jammy2026-10-27ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1078.80) @ jammy2026-10-27ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1073.73) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.134.145~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1024.25~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.133.143~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1075.74) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1075.71) @ jammy2026-10-27ubuntu
redhatkernel-rt-0:4.18.0-553.63.1.rt7.404.el8_102025-07-21redhat
redhatkernel-0:4.18.0-553.63.1.el8_102025-07-21redhat
redhatkernel-0:5.14.0-427.55.1.el9_42025-02-19redhat
redhatkernel-0:5.14.0-503.22.1.el9_52025-01-22redhat
linuxKernel @ 5.4.293 (fixes >=4.2.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 (45 versions)
  • every version up to 5.10.237-1: fixed in 5.10.237-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (30 versions)
  • every version up to 6.1.115-1: fixed in 6.1.115-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.6-1: fixed in 6.11.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.6-1: fixed in 6.11.6-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(22)

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 10× in last 7d / 42× 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 94 of 220 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 126 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% · 46th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  7. 2026-10-27 17:15 UTCEG score recompute
  8. 2026-10-27 17:15 UTCVendor advisory
  9. 2026-10-27 17:15 UTCGHSA enrichmentGHSA-r9cc-7xcq-fpxg · GitHub severity HIGH · GitHub CVSS 7.0
  10. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-25 16:59 UTCEG score recompute
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-10-19 18:01 UTCEG score recompute
  20. 2026-10-19 18:01 UTCVendor advisory
  21. 2026-10-19 18:00 UTCGHSA enrichmentGHSA-r9cc-7xcq-fpxg · GitHub severity HIGH · GitHub CVSS 7.0
  22. 2026-10-19 17:55 UTCOSV refresh
  23. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  24. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  25. 2026-10-18 06:55 UTCEG score recompute
Show 69 more
  1. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  2. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  3. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  4. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  5. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  6. 2026-10-12 17:41 UTCEG score recompute
  7. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  8. 2026-10-11 21:07 UTCEG score recompute
  9. 2026-10-11 15:59 UTCEG score recompute
  10. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  11. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  12. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  13. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  14. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  15. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  16. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  17. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  18. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  19. 2026-10-02 16:15 UTCEG score recompute
  20. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  21. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  22. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  23. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  25. 2026-09-26 22:42 UTCOSV refresh
  26. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  27. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  28. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  29. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  30. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  31. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  32. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  33. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  34. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  35. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  36. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  37. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  38. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  39. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  40. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  41. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  42. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  43. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  44. 2026-09-07 08:47 UTCOSV refresh
  45. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  46. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  47. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  48. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  49. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  50. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  51. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  52. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  53. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  54. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  55. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  56. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  57. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  58. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  59. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  60. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  61. 2026-08-20 18:01 UTCOSV refresh
  62. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  63. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  64. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  65. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  66. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  67. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  68. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  69. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.6% · 43rd percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-50154?
CVE-2024-50154 is a high-severity vulnerability; its CVE record was published on November 7, 2024. In the Linux kernel, the following vulnerability has been resolved: tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler(). """ We are seeing a use-after-free from a bpf prog attached to trace_tcp_retransmit_synack. The…
When was the CVE record for CVE-2024-50154 published?
The CVE record for CVE-2024-50154 was published on November 7, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-50154 actively exploited?
CVE-2024-50154 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50154?
CVE-2024-50154 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2024-50154?
A fix for CVE-2024-50154 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-50154 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-50154

Explore →

Is Your Infrastructure Affected by CVE-2024-50154?

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

Book a Demo →Browse All CVEs