CVE-2025-39955

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 2025-10-09. 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 — 4 sources updated this week

Also known asEUVD-2025-33328 (ENISA EUVD) · GHSA-63w2-9qrq-4h94 (GitHub Security Advisories)Source: ENISA EUVD

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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect().

syzbot reported the splat below where a socket had tcp_sk(sk)->fastopen_rsk in the TCP_ESTABLISHED state. [0]

syzbot reused the server-side TCP Fast Open socket as a new client before the TFO socket completes 3WHS:

  • accept()
  • connect(AF_UNSPEC)
  • connect() to another destination

As of accept(), sk->sk_state is TCP_SYN_RECV, and tcp_disconnect() changes it to TCP_CLOSE and makes connect() possible, which restarts timers.

Since tcp_disconnect() forgot to clear tcp_sk(sk)->fastopen_rsk, the retransmit timer triggered the warning and the intended packet was not retransmitted.

Let's call reqsk_fastopen_remove() in tcp_disconnect().

[0]: WARNING: CPU: 2 PID: 0 at net/ipv4/tcp_timer.c:542 tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7)) Modules linked in: CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 6.17.0-rc5-g201825fb4278 #62 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:tcp_retransmit_timer (net/ipv4/tcp_timer.c:542 (discriminator 7)) Code: 41 55 41 54 55 53 48 8b af b8 08 00 00 48 89 fb 48 85 ed 0f 84 55 01 00 00 0f b6 47 12 3c 03 74 0c 0f b6 47 12 3c 04 74 04 90 <0f> 0b 90 48 8b 85 c0 00 00 00 48 89 ef 48 8b 40 30 e8 6a 4f 06 3e RSP: 0018:ffffc900002f8d40 EFLAGS: 00010293 RAX: 0000000000000002 RBX: ffff888106911400 RCX: 0000000000000017 RDX: 0000000002517619 RSI: ffffffff83764080 RDI: ffff888106911400 RBP: ffff888106d5c000 R08: 0000000000000001 R09: ffffc900002f8de8 R10: 00000000000000c2 R11: ffffc900002f8ff8 R12: ffff888106911540 R13: ffff888106911480 R14: ffff888106911840 R15: ffffc900002f8de0 FS: 0000000000000000(0000) GS:ffff88907b768000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8044d69d90 CR3: 0000000002c30003 CR4: 0000000000370ef0 Call Trace: tcp_write_timer (net/ipv4/tcp_timer.c:738) call_timer_fn (kernel/time/timer.c:1747) __run_timers (kernel/time/timer.c:1799 kernel/time/timer.c:2372) timer_expire_remote (kernel/time/timer.c:2385 kernel/time/timer.c:2376 kernel/time/timer.c:2135) tmigr_handle_remote_up (kernel/time/timer_migration.c:944 kernel/time/timer_migration.c:1035) __walk_groups.isra.0 (kernel/time/timer_migration.c:533 (discriminator 1)) tmigr_handle_remote (kernel/time/timer_migration.c:1096) handle_softirqs (./arch/x86/include/asm/jump_label.h:36 ./include/trace/events/irq.h:142 kernel/softirq.c:580) irq_exit_rcu (kernel/softirq.c:614 kernel/softirq.c:453 kernel/softirq.c:680 kernel/softirq.c:696) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1050 (discriminator 35) arch/x86/kernel/apic/apic.c:1050 (discriminator 35))

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.2% × 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.2%
EPSS %ILE
5th
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.2% within 30 daysSource: FIRST EPSS. 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: 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.

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

October 9, 2025

Last Modified

October 19, 2026

Advisory Details (9)

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

tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ec092a91ff351dcde89c23e795b73a328274db6
Web page

tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45c8a6cc2bcd780e634a6ba8e46bffbdf1fc5c01
Web page

tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33a4fdf0b4a25f8ce65380c3b0136b407ca57609
Web page

tcp: Clear tcp_sk(sk)->fastopen_rsk in tcp_disconnect(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17d699727577814198d744d6afe54735c6b54c99

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-27ubuntu
redhatkernel-0:3.10.0-1160.144.1.el72025-12-22redhat
redhatkernel-rt-0:3.10.0-1160.144.1.rt56.1296.el72025-12-22redhat
redhatkernel-0:4.18.0-305.182.1.el8_42025-12-17redhat
redhatkernel-0:4.18.0-193.178.1.el8_22025-12-17redhat
redhatkernel-0:5.14.0-70.158.1.el9_02025-12-17redhat
redhatkernel-0:4.18.0-372.173.1.el8_62025-12-17redhat
redhatkernel-0:5.14.0-427.103.1.el9_42025-12-17redhat
redhatkernel-0:4.18.0-477.123.1.el8_82025-12-17redhat
redhatkernel-rt-0:5.14.0-284.150.1.rt14.435.el9_22025-12-17redhat
redhatkernel-rt-0:5.14.0-70.158.1.rt21.230.el9_02025-12-17redhat
redhatkernel-0:5.14.0-284.150.1.el9_22025-12-17redhat
redhatkernel-0:6.12.0-55.47.1.el10_02025-12-02redhat
redhatkernel-0:4.18.0-553.87.1.el8_102025-12-01redhat
redhatkernel-0:5.14.0-570.69.1.el9_62025-12-01redhat
redhatkernel-0:5.14.0-611.11.1.el9_72025-12-01redhat
redhatkernel-rt-0:4.18.0-553.87.1.rt7.428.el8_102025-12-01redhat
redhatkernel-0:6.12.0-124.13.1.el10_12025-11-24redhat
linuxKernel @ 5.4.300 (fixes >=3.7.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 (47 versions)
  • every version up to 5.10.247-1: fixed in 5.10.247-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.153-1~deb11u1 (12 versions)
  • every version up to 6.1.158-1~deb11u1: fixed in 6.1.158-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (44 versions)
  • every version up to 6.1.158-1: fixed in 6.1.158-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.57-1~bpo12+1 (6 versions)
  • every version up to 6.12.57-1: fixed in 6.12.57-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (67 versions)
  • every version up to 6.16.9-1: fixed in 6.16.9-1
—

Additional Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 11× in last 7d / 45× 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 98 of 192 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 94 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-39955?
CVE-2025-39955 is a high-severity vulnerability; its CVE record was published on October 9, 2025. In the Linux kernel, the following vulnerability has been resolved: tcp: Clear tcpsk(sk)->fastopenrsk in tcp_disconnect(). syzbot reported the splat below where a socket had tcpsk(sk)->fastopenrsk in the TCP_ESTABLISHED state. [0] syzbot reused the server-side TCP Fast Open socket as a new client…
When was the CVE record for CVE-2025-39955 published?
The CVE record for CVE-2025-39955 was published on October 9, 2025. 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 19, 2026; the record at its source may have been updated since.
Is CVE-2025-39955 actively exploited?
CVE-2025-39955 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39955?
CVE-2025-39955 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-39955?
A fix for CVE-2025-39955 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39955 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-2025-39955

Explore →

Is Your Infrastructure Affected by CVE-2025-39955?

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