CVE-2025-38250

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-07-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-20811 (ENISA EUVD) · GHSA-6r74-5vg7-24jv (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: hci_core: Fix use-after-free in vhci_flush()

syzbot reported use-after-free in vhci_flush() without repro. [0]

From the splat, a thread close()d a vhci file descriptor while its device was being used by iotcl() on another thread.

Once the last fd refcnt is released, vhci_release() calls hci_unregister_dev(), hci_free_dev(), and kfree() for struct vhci_data, which is set to hci_dev->dev->driver_data.

The problem is that there is no synchronisation after unlinking hdev from hci_dev_list in hci_unregister_dev(). There might be another thread still accessing the hdev which was fetched before the unlink operation.

We can use SRCU for such synchronisation.

Let's run hci_dev_reset() under SRCU and wait for its completion in hci_unregister_dev().

Another option would be to restore hci_dev->destruct(), which was removed in commit 587ae086f6e4 ("Bluetooth: Remove unused hci-destruct cb"). However, this would not be a good solution, as we should not run hci_unregister_dev() while there are in-flight ioctl() requests, which could lead to another data-race KCSAN splat.

Note that other drivers seem to have the same problem, for exmaple, virtbt_remove().

[0]: BUG: KASAN: slab-use-after-free in skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline] BUG: KASAN: slab-use-after-free in skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937 Read of size 8 at addr ffff88807cb8d858 by task syz.1.219/6718

CPU: 1 UID: 0 PID: 6718 Comm: syz.1.219 Not tainted 6.16.0-rc1-syzkaller-00196-g08207f42d3ff #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xd2/0x2b0 mm/kasan/report.c:521 kasan_report+0x118/0x150 mm/kasan/report.c:634 skb_queue_empty_lockless include/linux/skbuff.h:1891 [inline] skb_queue_purge_reason+0x99/0x360 net/core/skbuff.c:3937 skb_queue_purge include/linux/skbuff.h:3368 [inline] vhci_flush+0x44/0x50 drivers/bluetooth/hci_vhci.c:69 hci_dev_do_reset net/bluetooth/hci_core.c:552 [inline] hci_dev_reset+0x420/0x5c0 net/bluetooth/hci_core.c:592 sock_do_ioctl+0xd9/0x300 net/socket.c:1190 sock_ioctl+0x576/0x790 net/socket.c:1311 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 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 RIP: 0033:0x7fcf5b98e929 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:00007fcf5c7b9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fcf5bbb6160 RCX: 00007fcf5b98e929 RDX: 0000000000000000 RSI: 00000000400448cb RDI: 0000000000000009 RBP: 00007fcf5ba10b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fcf5bbb6160 R15: 00007ffd6353d528

Allocated by task 6535: 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] vhci_open+0x57/0x360 drivers/bluetooth/hci_vhci.c:635 misc_open+0x2bc/0x330 drivers/char/misc.c:161 chrdev_open+0x4c9/0x5e0 fs/char_dev.c:414 do_dentry_open+0xdf0/0x1970 fs/open.c:964 vfs_open+0x3b/0x340 fs/open.c:1094 do_open fs/namei.c:3887 [inline] path_openat+0x2ee5/0x3830 fs/name ---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
7th
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-28). 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

July 9, 2025

Last Modified

October 15, 2026

Advisory Details (6)

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

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

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

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

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

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

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

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

https://git.kernel.org/stable/c/90dee0a0ff84fac8accd5be98412b3819f667149
Web page

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

https://git.kernel.org/stable/c/1d6123102e9fbedc8d25bf4731da6d513173e49e
Web page

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

https://git.kernel.org/stable/c/0e5c144c557df910ab64d9c25d06399a9a735e65

Vendor Advisories for CVE-2025-38250(15)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-29ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-29ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-29ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-29ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-29ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-29ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-29ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-29ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-29ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-29ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-29ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-29ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-29ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-29ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1018.19~24.04.1) @ noble2026-10-29ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1014.14~24.04.1) @ noble2026-10-29ubuntu
redhatkernel-0:5.14.0-70.146.1.el9_02025-09-11redhat
redhatkernel-0:5.14.0-427.88.1.el9_42025-09-11redhat
redhatkernel-rt-0:5.14.0-70.146.1.rt21.218.el9_02025-09-10redhat
redhatkernel-0:5.14.0-284.136.1.el9_22025-09-04redhat
redhatkernel-rt-0:5.14.0-284.136.1.rt14.421.el9_22025-09-04redhat
redhatkernel-0:4.18.0-477.108.1.el8_82025-09-02redhat
redhatkernel-0:4.18.0-305.170.1.el8_42025-09-02redhat
redhatkernel-0:4.18.0-372.158.1.el8_62025-08-27redhat
redhatkernel-0:4.18.0-193.165.1.el8_22025-08-27redhat
redhatkernel-0:4.18.0-553.70.1.el8_102025-08-18redhat
redhatkernel-0:5.14.0-570.35.1.el9_62025-08-18redhat
redhatkernel-0:6.12.0-55.28.1.el10_02025-08-18redhat
redhatkernel-rt-0:4.18.0-553.70.1.rt7.411.el8_102025-08-18redhat
linuxKernel @ 5.10.259 (fixes >=3.4.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 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)
  • every version up to 6.1.170-1~deb11u1: fixed in 6.1.170-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38250?
CVE-2025-38250 is a high-severity vulnerability; its CVE record was published on July 9, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_core: Fix use-after-free in vhci_flush() syzbot reported use-after-free in vhci_flush() without repro. [0] From the splat, a thread close()d a vhci file descriptor while its device was being used by iotcl() on…
When was the CVE record for CVE-2025-38250 published?
The CVE record for CVE-2025-38250 was published on July 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 15, 2026; the record at its source may have been updated since.
Is CVE-2025-38250 actively exploited?
CVE-2025-38250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38250?
CVE-2025-38250 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38250?
A fix for CVE-2025-38250 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38250 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-38250

Explore →

Is Your Infrastructure Affected by CVE-2025-38250?

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

Book a Demo →Browse All CVEs