CVE-2024-50083

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2024-10-29. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.5EG
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.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tcp: fix mptcp DSS corruption due to large pmtu xmit

Syzkaller was able to trigger a DSS corruption:

TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Modules linked in: CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 <0f> 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff RSP: 0018:ffffc90000006db8 EFLAGS: 00010246 RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00 RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0 RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8 R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000 R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5 FS: 000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: move_skbs_to_msk net/mptcp/protocol.c:811 [inline] mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854 subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490 tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283 tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350 ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 __netif_receive_skb_one_core net/core/dev.c:5662 [inline] __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775 process_backlog+0x662/0x15b0 net/core/dev.c:6107 __napi_poll+0xcb/0x490 net/core/dev.c:6771 napi_poll net/core/dev.c:6840 [inline] net_rx_action+0x89b/0x1240 net/core/dev.c:6962 handle_softirqs+0x2c5/0x980 kernel/softirq.c:554 do_softirq+0x11b/0x1e0 kernel/softirq.c:455 __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline] __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451 dev_queue_xmit include/linux/netdevice.h:3094 [inline] neigh_hh_output include/net/neighbour.h:526 [inline] neigh_output include/net/neighbour.h:540 [inline] ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236 ip_local_out net/ipv4/ip_output.c:130 [inline] __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536 __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline] tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752 __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015 tcp_push_pending_frames include/net/tcp.h:2107 [inline] tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline] tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 sk_backlog_rcv include/net/sock.h:1113 [inline] __release_sock+0x214/0x350 net/core/sock.c:3072 release_sock+0x61/0x1f0 net/core/sock.c:3626 mptcp_push_ ---truncated---

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.9% × 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.9%
EPSS %ILE
57th
KEV
Not listed

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.

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

October 29, 2024

Last Modified

November 3, 2025

References (9)

Vendor Advisories for CVE-2024-50083(1)

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

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.133.132) @ jammy2026-05-23ubuntu
ubuntulinux-tools-ibm (5.15.0.1070.66) @ jammy2026-05-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1077.86~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1075.81~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1073.73) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1075.71) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1072.70) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1078.80) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.134.145~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.133.143~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-virtual (6.8.0-56.58) @ noble2026-05-23ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1022.22) @ noble2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1018.19) @ noble2026-05-23ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-05-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-05-23ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-05-23ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-05-23ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-05-23ubuntu
linuxKernel @ 5.10.228 (fixes >=5.6.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
  • 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.5-1: fixed in 6.11.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.5-1: fixed in 6.11.5-1
—

Additional Vendor Advisories

(24)

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 11× in last 7d / 32× 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 89 of 186 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. 11 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-50083?
CVE-2024-50083 is a high-severity vulnerability; its CVE record was published on October 29, 2024. In the Linux kernel, the following vulnerability has been resolved: tcp: fix mptcp DSS corruption due to large pmtu xmit Syzkaller was able to trigger a DSS corruption: TCP: requestsocksubflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies. ------------[ cut here ]------------…
When was the CVE record for CVE-2024-50083 published?
The CVE record for CVE-2024-50083 was published on October 29, 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 November 3, 2025; the record at its source may have been updated since.
Is CVE-2024-50083 actively exploited?
CVE-2024-50083 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-50083?
CVE-2024-50083 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-50083?
A fix for CVE-2024-50083 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-50083 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-50083

Explore →

Is Your Infrastructure Affected by CVE-2024-50083?

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

Book a Demo →Browse All CVEs