CVE-2025-39913

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-01. 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-32662 (ENISA EUVD) · GHSA-36qj-697h-rh8p (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_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork.

syzbot reported the splat below. [0]

The repro does the following:

  • Load a sk_msg prog that calls bpf_msg_cork_bytes(msg, cork_bytes)
  • Attach the prog to a SOCKMAP
  • Add a socket to the SOCKMAP
  • Activate fault injection
  • Send data less than cork_bytes

At 5., the data is carried over to the next sendmsg() as it is smaller than the cork_bytes specified by bpf_msg_cork_bytes().

Then, tcp_bpf_send_verdict() tries to allocate psock->cork to hold the data, but this fails silently due to fault injection + __GFP_NOWARN.

If the allocation fails, we need to revert the sk->sk_forward_alloc change done by sk_msg_alloc().

Let's call sk_msg_free() when tcp_bpf_send_verdict fails to allocate psock->cork.

The "*copied" also needs to be updated such that a proper error can be returned to the caller, sendmsg. It fails to allocate psock->cork. Nothing has been corked so far, so this patch simply sets "*copied" to 0.

[0]: WARNING: net/ipv4/af_inet.c:156 at inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156, CPU#1: syz-executor/5983 Modules linked in: CPU: 1 UID: 0 PID: 5983 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 RIP: 0010:inet_sock_destruct+0x623/0x730 net/ipv4/af_inet.c:156 Code: 0f 0b 90 e9 62 fe ff ff e8 7a db b5 f7 90 0f 0b 90 e9 95 fe ff ff e8 6c db b5 f7 90 0f 0b 90 e9 bb fe ff ff e8 5e db b5 f7 90 <0f> 0b 90 e9 e1 fe ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 9f fc RSP: 0018:ffffc90000a08b48 EFLAGS: 00010246 RAX: ffffffff8a09d0b2 RBX: dffffc0000000000 RCX: ffff888024a23c80 RDX: 0000000000000100 RSI: 0000000000000fff RDI: 0000000000000000 RBP: 0000000000000fff R08: ffff88807e07c627 R09: 1ffff1100fc0f8c4 R10: dffffc0000000000 R11: ffffed100fc0f8c5 R12: ffff88807e07c380 R13: dffffc0000000000 R14: ffff88807e07c60c R15: 1ffff1100fc0f872 FS: 00005555604c4500(0000) GS:ffff888125af1000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005555604df5c8 CR3: 0000000032b06000 CR4: 00000000003526f0 Call Trace: __sk_destruct+0x86/0x660 net/core/sock.c:2339 rcu_do_batch kernel/rcu/tree.c:2605 [inline] rcu_core+0xca8/0x1770 kernel/rcu/tree.c:2861 handle_softirqs+0x286/0x870 kernel/softirq.c:579 __do_softirq kernel/softirq.c:613 [inline] invoke_softirq kernel/softirq.c:453 [inline] __irq_exit_rcu+0xca/0x1f0 kernel/softirq.c:680 irq_exit_rcu+0x9/0x30 kernel/softirq.c:696 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1052 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1052

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
8th
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 (model v2026.06.15, score date 2026-11-03). 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

October 1, 2025

Last Modified

October 19, 2026

Advisory Details (9)

Auto-updated Jun 6, 2026
Patch available.
Web page

SSA-253495

https://cert-portal.siemens.com/productcert/html/ssa-253495.html
Web page

tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c2a6456bdf9794474460d885c359b6c4522d6e3
Web page

tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7429b8b9bfbc276fd304fbaebc405f46b421fedf
Web page

tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66bcb04a441fbf15d66834b7e3eefb313dd750c8
Web page

tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/539920180c55f5e13a2488a2339f94e6b8cb69e0
Web page

tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08f58d10f5abf11d297cc910754922498c921f91
Web page

tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05366527f44cf4b884f3d9462ae8009be9665856

Vendor Advisories for CVE-2025-39913(2)

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

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.170.159) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1052.52) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1097.93) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1041.43) @ jammy2026-10-27ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1095.95) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1064 (5.15.0-1064.68) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1099.103) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1100.90) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1095.95) @ jammy2026-10-27ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1100.107~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-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-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-27ubuntu
linuxKernel @ 5.4.300 (fixes >=4.17.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.148-1~deb11u1 (11 versions)
  • every version up to 6.1.153-1~deb11u1: fixed in 6.1.153-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (43 versions)
  • every version up to 6.1.153-1: fixed in 6.1.153-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1, 6.12.43-1~bpo12+1
  • every version up to 6.12.48-1: fixed in 6.12.48-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (66 versions)
  • every version up to 6.16.8-1: fixed in 6.16.8-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 9× in last 7d / 48× 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 202 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 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-39913?
CVE-2025-39913 is a high-severity vulnerability; its CVE record was published on October 1, 2025. In the Linux kernel, the following vulnerability has been resolved: tcp_bpf: Call sk_msg_free() when tcp_bpf_send_verdict() fails to allocate psock->cork. syzbot reported the splat below. [0] The repro does the following: 1. Load a sk_msg prog that calls bpf_msg_cork_bytes(msg, cork_bytes) 2.…
When was the CVE record for CVE-2025-39913 published?
The CVE record for CVE-2025-39913 was published on October 1, 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-39913 actively exploited?
CVE-2025-39913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39913?
CVE-2025-39913 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-39913?
A fix for CVE-2025-39913 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39913 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-39913

Explore →

Is Your Infrastructure Affected by CVE-2025-39913?

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

Book a Demo →Browse All CVEs