CVE-2025-39860

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-09-22. 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-30340 (ENISA EUVD) · GHSA-c684-q9wg-vhh9 (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:

Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen()

syzbot reported the splat below without a repro.

In the splat, a single thread calling bt_accept_dequeue() freed sk and touched it after that.

The root cause would be the racy l2cap_sock_cleanup_listen() call added by the cited commit.

bt_accept_dequeue() is called under lock_sock() except for l2cap_sock_release().

Two threads could see the same socket during the list iteration in bt_accept_dequeue():

CPU1 CPU2 (close()) ---- ---- sock_hold(sk) sock_hold(sk); lock_sock(sk) <-- block close() sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- refcnt by bt_accept_enqueue() release_sock(sk) lock_sock(sk) sock_put(sk) bt_accept_unlink(sk) sock_put(sk) <-- last refcnt bt_accept_unlink(sk) <-- UAF

Depending on the timing, the other thread could show up in the "Freed by task" part.

Let's call l2cap_sock_cleanup_listen() under lock_sock() in l2cap_sock_release().

[0]: BUG: KASAN: slab-use-after-free in debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] BUG: KASAN: slab-use-after-free in do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 Read of size 4 at addr ffff88803b7eb1c4 by task syz.5.3276/16995 CPU: 3 UID: 0 PID: 16995 Comm: syz.5.3276 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcd/0x630 mm/kasan/report.c:482 kasan_report+0xe0/0x110 mm/kasan/report.c:595 debug_spin_lock_before kernel/locking/spinlock_debug.c:86 [inline] do_raw_spin_lock+0x26f/0x2b0 kernel/locking/spinlock_debug.c:115 spin_lock_bh include/linux/spinlock.h:356 [inline] release_sock+0x21/0x220 net/core/sock.c:3746 bt_accept_dequeue+0x505/0x600 net/bluetooth/af_bluetooth.c:312 l2cap_sock_cleanup_listen+0x5c/0x2a0 net/bluetooth/l2cap_sock.c:1451 l2cap_sock_release+0x5c/0x210 net/bluetooth/l2cap_sock.c:1425 __sock_release+0xb3/0x270 net/socket.c:649 sock_close+0x1c/0x30 net/socket.c:1439 __fput+0x3ff/0xb70 fs/file_table.c:468 task_work_run+0x14d/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xeb/0x110 kernel/entry/common.c:43 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline] do_syscall_64+0x3f6/0x4c0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f2accf8ebe9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffdb6cb1378 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 00000000000426fb RCX: 00007f2accf8ebe9 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 00007f2acd1b7da0 R08: 0000000000000001 R09: 00000012b6cb166f R10: 0000001b30e20000 R11: 0000000000000246 R12: 00007f2acd1b609c R13: 00007f2acd1b6090 R14: ffffffffffffffff R15: 00007ffdb6cb1490

Allocated by task 5326: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:388 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:405 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4365 [inline] __kmalloc_nopro ---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.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
14th
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-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

September 19, 2025

Last Modified

October 19, 2026

Advisory Details (10)

Auto-updated May 12, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4328-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4327-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
Web page

Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/964cbb198f9c46c2b2358cd1faffc04c1e8248cf
Web page

Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/862c628108562d8c7a516a900034823b381d3cba
Web page

Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83e1d9892ef51785cf0760b7681436760dda435a
Web page

Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6077d16b5c0f65d571eee709de2f0541fb5ef0ca
Web page

Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47f6090bcf75c369695d21c3f179db8a56bbbd49
Web page

Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3dff390f55ccd9ce12e91233849769b5312180c2
Web page

Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/306b0991413b482dbf5585b423022123bb505966
Web page

Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ca99fc3512a8074de20ee52a87b492dfcc41a4d

Vendor Advisories for CVE-2025-39860(1)

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

Patch Availability(21)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1096.100) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1061 (5.15.0-1061.65) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gkeop-5.15 (5.15.0.1080.79) @ jammy2026-10-27ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1089.85) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1091.89) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1102.111~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1097.87) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1101.99) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-10-27ubuntu
ubuntuoracle (6.8.0-1005) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1101.86) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-27ubuntu
linuxKernel @ 5.4.299 (fixes >=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 (46 versions)
  • every version up to 5.10.244-1: fixed in 5.10.244-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 (64 versions)
  • every version up to 6.16.6-1: fixed in 6.16.6-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(20)

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 / 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 231 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 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-39860?
CVE-2025-39860 is a high-severity vulnerability; its CVE record was published on September 19, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free in l2cap_sock_cleanup_listen() syzbot reported the splat below without a repro. In the splat, a single thread calling bt_accept_dequeue() freed sk and touched it after that. The root cause would be the…
When was the CVE record for CVE-2025-39860 published?
The CVE record for CVE-2025-39860 was published on September 19, 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-39860 actively exploited?
CVE-2025-39860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39860?
CVE-2025-39860 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-39860?
A fix for CVE-2025-39860 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39860 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-39860

Explore →

Is Your Infrastructure Affected by CVE-2025-39860?

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

Book a Demo →Browse All CVEs