CVE-2025-39982

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-15. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2025-34590 (ENISA EUVD) · GHSA-jm87-4mhh-83rp (GitHub Security Advisories)Source: ENISA EUVD

8.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.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync

This fixes the following UFA in hci_acl_create_conn_sync where a connection still pending is command submission (conn->state == BT_OPEN) maybe freed, also since this also can happen with the likes of hci_le_create_conn_sync fix it as well:

BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5ef/0x790 net/bluetooth/hci_sync.c:6861 Write of size 2 at addr ffff88805ffcc038 by task kworker/u11:2/9541

CPU: 1 UID: 0 PID: 9541 Comm: kworker/u11:2 Not tainted 6.16.0-rc7 #3 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 Workqueue: hci3 hci_cmd_sync_work Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x230 mm/kasan/report.c:480 kasan_report+0x118/0x150 mm/kasan/report.c:593 hci_acl_create_conn_sync+0x5ef/0x790 net/bluetooth/hci_sync.c:6861 hci_cmd_sync_work+0x210/0x3a0 net/bluetooth/hci_sync.c:332 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16-rc7/arch/x86/entry/entry_64.S:245

Allocated by task 123736: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __kmalloc_cache_noprof+0x230/0x3d0 mm/slub.c:4359 kmalloc_noprof include/linux/slab.h:905 [inline] kzalloc_noprof include/linux/slab.h:1039 [inline] __hci_conn_add+0x233/0x1b30 net/bluetooth/hci_conn.c:939 hci_conn_add_unset net/bluetooth/hci_conn.c:1051 [inline] hci_connect_acl+0x16c/0x4e0 net/bluetooth/hci_conn.c:1634 pair_device+0x418/0xa70 net/bluetooth/mgmt.c:3556 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:712 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:727 sock_write_iter+0x258/0x330 net/socket.c:1131 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x54b/0xa90 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 103680: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:576 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x62/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2381 [inline] slab_free mm/slub.c:4643 [inline] kfree+0x18e/0x440 mm/slub.c:4842 device_release+0x9c/0x1c0 kobject_cleanup lib/kobject.c:689 [inline] kobject_release lib/kobject.c:720 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x22b/0x480 lib/kobject.c:737 hci_conn_cleanup net/bluetooth/hci_conn.c:175 [inline] hci_conn_del+0x8ff/0xcb0 net/bluetooth/hci_conn.c:1173 hci_conn_complete_evt+0x3c7/0x1040 net/bluetooth/hci_event.c:3199 hci_event_func net/bluetooth/hci_event.c:7477 [inline] hci_event_packet+0x7e0/0x1200 net/bluetooth/hci_event.c:7531 hci_rx_work+0x46a/0xe80 net/bluetooth/hci_core.c:4070 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/sour ---truncated---

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
20th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% 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: 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 15, 2025

Last Modified

October 19, 2026

Advisory Details (5)

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

Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6243bda271a628c48875e3e473206e7f584892ce
Web page

Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/484c7d571a3d1b3fd298fa691b660438c4548a53

Vendor Advisories for CVE-2025-39982(11)

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

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
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-aws-edge (6.8.0-1050.53~22.04.1) @ 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
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-10-27ubuntu
redhatkernel-0:5.14.0-570.129.1.el9_62026-07-23redhat
redhatkernel-rt-0:5.14.0-284.152.1.rt14.437.el9_22026-01-14redhat
redhatkernel-rt-0:5.14.0-70.161.1.rt21.233.el9_02026-01-14redhat
redhatkernel-0:5.14.0-284.152.1.el9_22026-01-14redhat
redhatkernel-0:5.14.0-70.161.1.el9_02026-01-14redhat
redhatkernel-0:5.14.0-427.106.1.el9_42026-01-13redhat
redhatkernel-0:6.12.0-55.52.1.el10_02026-01-08redhat
redhatkernel-0:6.12.0-124.20.1.el10_12025-12-09redhat
redhatkernel-0:5.14.0-611.8.1.el9_72025-11-17redhat
linuxKernel @ 6.1.155 (fixes >=5.18.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
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 (68 versions)
  • every version up to 6.16.10-1: fixed in 6.16.10-1
—

Additional Vendor Advisories

(10)

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-39982?
CVE-2025-39982 is a high-severity vulnerability; its CVE record was published on October 15, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcievent: Fix UAF in hciaclcreateconn_sync This fixes the following UFA in hciaclcreateconnsync where a connection still pending is command submission (conn->state == BT_OPEN) maybe freed, also since this also can happen…
When was the CVE record for CVE-2025-39982 published?
The CVE record for CVE-2025-39982 was published on October 15, 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-39982 actively exploited?
CVE-2025-39982 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39982?
CVE-2025-39982 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-39982?
A fix for CVE-2025-39982 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39982 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-39982

Explore →

Is Your Infrastructure Affected by CVE-2025-39982?

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

Book a Demo →Browse All CVEs