CVE-2024-26782

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

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

A fix is available — apply it.

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

mptcp: fix double-free on socket dismantle

when MPTCP server accepts an incoming connection, it clones its listener socket. However, the pointer to 'inet_opt' for the new socket has the same value as the original one: as a consequence, on program exit it's possible to observe the following splat:

BUG: KASAN: double-free in inet_sock_destruct+0x54f/0x8b0 Free of addr ffff888485950880 by task swapper/25/0

CPU: 25 PID: 0 Comm: swapper/25 Kdump: loaded Not tainted 6.8.0-rc1+ #609 Hardware name: Supermicro SYS-6027R-72RF/X9DRH-7TF/7F/iTF/iF, BIOS 3.0 07/26/2013 Call Trace: dump_stack_lvl+0x32/0x50 print_report+0xca/0x620 kasan_report_invalid_free+0x64/0x90 __kasan_slab_free+0x1aa/0x1f0 kfree+0xed/0x2e0 inet_sock_destruct+0x54f/0x8b0 __sk_destruct+0x48/0x5b0 rcu_do_batch+0x34e/0xd90 rcu_core+0x559/0xac0 __do_softirq+0x183/0x5a4 irq_exit_rcu+0x12d/0x170 sysvec_apic_timer_interrupt+0x6b/0x80 asm_sysvec_apic_timer_interrupt+0x16/0x20 RIP: 0010:cpuidle_enter_state+0x175/0x300 Code: 30 00 0f 84 1f 01 00 00 83 e8 01 83 f8 ff 75 e5 48 83 c4 18 44 89 e8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc fb 45 85 ed <0f> 89 60 ff ff ff 48 c1 e5 06 48 c7 43 18 00 00 00 00 48 83 44 2b RSP: 0018:ffff888481cf7d90 EFLAGS: 00000202 RAX: 0000000000000000 RBX: ffff88887facddc8 RCX: 0000000000000000 RDX: 1ffff1110ff588b1 RSI: 0000000000000019 RDI: ffff88887fac4588 RBP: 0000000000000004 R08: 0000000000000002 R09: 0000000000043080 R10: 0009b02ea273363f R11: ffff88887fabf42b R12: ffffffff932592e0 R13: 0000000000000004 R14: 0000000000000000 R15: 00000022c880ec80 cpuidle_enter+0x4a/0xa0 do_idle+0x310/0x410 cpu_startup_entry+0x51/0x60 start_secondary+0x211/0x270 secondary_startup_64_no_verify+0x184/0x18b

Allocated by task 6853: kasan_save_stack+0x1c/0x40 kasan_save_track+0x10/0x30 __kasan_kmalloc+0xa6/0xb0 __kmalloc+0x1eb/0x450 cipso_v4_sock_setattr+0x96/0x360 netlbl_sock_setattr+0x132/0x1f0 selinux_netlbl_socket_post_create+0x6c/0x110 selinux_socket_post_create+0x37b/0x7f0 security_socket_post_create+0x63/0xb0 __sock_create+0x305/0x450 __sys_socket_create.part.23+0xbd/0x130 __sys_socket+0x37/0xb0 __x64_sys_socket+0x6f/0xb0 do_syscall_64+0x83/0x160 entry_SYSCALL_64_after_hwframe+0x6e/0x76

Freed by task 6858: kasan_save_stack+0x1c/0x40 kasan_save_track+0x10/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x12c/0x1f0 kfree+0xed/0x2e0 inet_sock_destruct+0x54f/0x8b0 __sk_destruct+0x48/0x5b0 subflow_ulp_release+0x1f0/0x250 tcp_cleanup_ulp+0x6e/0x110 tcp_v4_destroy_sock+0x5a/0x3a0 inet_csk_destroy_sock+0x135/0x390 tcp_fin+0x416/0x5c0 tcp_data_queue+0x1bc8/0x4310 tcp_rcv_state_process+0x15a3/0x47b0 tcp_v4_do_rcv+0x2c1/0x990 tcp_v4_rcv+0x41fb/0x5ed0 ip_protocol_deliver_rcu+0x6d/0x9f0 ip_local_deliver_finish+0x278/0x360 ip_local_deliver+0x182/0x2c0 ip_rcv+0xb5/0x1c0 __netif_receive_skb_one_core+0x16e/0x1b0 process_backlog+0x1e3/0x650 __napi_poll+0xa6/0x500 net_rx_action+0x740/0xbb0 __do_softirq+0x183/0x5a4

The buggy address belongs to the object at ffff888485950880 which belongs to the cache kmalloc-64 of size 64 The buggy address is located 0 bytes inside of 64-byte region [ffff888485950880, ffff8884859508c0)

The buggy address belongs to the physical page: page:0000000056d1e95e refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888485950700 pfn:0x485950 flags: 0x57ffffc0000800(slab|node=1|zone=2|lastcpupid=0x1fffff) page_type: 0xffffffff() raw: 0057ffffc0000800 ffff88810004c640 ffffea00121b8ac0 dead000000000006 raw: ffff888485950700 0000000000200019 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff888485950780: fa fb fb ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.7%
EPSS %ILE
53rd
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 Vulnrichment) · Technical impact partial (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

April 4, 2024

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 4, 2026
Patch available.
Web page

mptcp: fix double-free on socket dismantle - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: fix double-free on socket dismantle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85933e80d077c9ae2227226beb86c22f464059cc
Web page

mptcp: fix double-free on socket dismantle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a4eeb6912538c2d0b158e8d11b62d96c1dada4e
Web page

mptcp: fix double-free on socket dismantle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10048689def7e40a4405acda16fdc6477d4ecc5c
Web page

mptcp: fix double-free on socket dismantle - kernel/git/stable/linux.git - Linux kernel stable tree

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

mptcp: fix double-free on socket dismantle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d93fd40c62397326046902a2c5cb75af50882a85

Vendor Advisories for CVE-2024-26782(2)

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

Patch Availability(18)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-kvm (5.15.0.1060.56) @ jammy2026-10-20ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.44.44) @ mantic2026-10-20ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.113.123~20.04.1) @ focal2026-10-20ubuntu
ubuntulinux-tools-nvidia-lowlatency (5.15.0.1058.58) @ jammy2026-10-20ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-10-20ubuntu
ubuntulinux-tools-gcp (6.5.0.1024.26~22.04.1) @ jammy2026-10-20ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1030.34) @ jammy2026-10-20ubuntu
ubuntulinux-tools-starfive (6.5.0.1017.18~22.04.1) @ jammy2026-10-20ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1058.64~20.04.1) @ focal2026-10-20ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1066.64) @ jammy2026-10-20ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1063.63) @ jammy2026-10-20ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1057.60~20.04.1) @ focal2026-10-20ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1027.29) @ jammy2026-10-20ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.44.44~22.04.1) @ jammy2026-10-20ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1061.57) @ jammy2026-10-20ubuntu
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-0:4.18.0-553.5.1.el8_102024-06-05redhat
linuxKernel @ 5.10.212 (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 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux-5.105.10.136-1~deb10u1 ... 5.10.209-2~deb10u1 (13 versions)
  • every version up to 5.10.216-1~deb10u1: fixed in 5.10.216-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)
  • every version up to 5.10.216-1: fixed in 5.10.216-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (18 versions)
  • every version up to 6.1.82-1: fixed in 6.1.82-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.9-1: fixed in 6.7.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.9-1: fixed in 6.7.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

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 / 35× 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 96 of 205 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26782?
CVE-2024-26782 is a high-severity vulnerability; its CVE record was published on April 4, 2024. In the Linux kernel, the following vulnerability has been resolved: mptcp: fix double-free on socket dismantle when MPTCP server accepts an incoming connection, it clones its listener socket. However, the pointer to 'inet_opt' for the new socket has the same value as the original one: as a…
When was the CVE record for CVE-2024-26782 published?
The CVE record for CVE-2024-26782 was published on April 4, 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-26782 actively exploited?
CVE-2024-26782 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26782?
CVE-2024-26782 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-26782?
A fix for CVE-2024-26782 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26782 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-26782

Explore →

Is Your Infrastructure Affected by CVE-2024-26782?

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

Book a Demo →Browse All CVEs