SECUFOCUSNOW
Home›CVE index›CVE-2025-38250
Review reviewHigh

CVE-2025-38250

Linux Linux, linux kernel

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(). The...

CVSS
7.8
EPSS
0.14%
4.22% percentile
CISA KEV
Not listed
Published
2025.07.09
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

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(). The...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= bf18c7118cf83ad4b9aa476354b4a06bcb9d0c4f < dd4becd3fd4102696e1c15e6d260a1712a2d8685, >= bf18c7118cf83ad4b9aa476354b4a06bcb9d0c4f < 90dee0a0ff84fac8accd5be98412b3819f667149, >= bf18c7118cf83ad4b9aa476354b4a06bcb9d0c4f < c56b177efce8b62798e4d96bdb9867106cb7c4a0, >= bf18c7118cf83ad4b9aa476354b4a06bcb9d0c4f < bc0819a25e04cd68ef3568cfa51b63118fea39a7, >= bf18c7118cf83ad4b9aa476354b4a06bcb9d0c4f < ce23b73f0f27e2dbeb81734a79db710f05aa33c6, >= bf18c7118cf83ad4b9aa476354b4a06bcb9d0c4f < 0e5c144c557df910ab64d9c25d06399a9a735e65, >= bf18c7118cf83ad4b9aa476354b4a06bcb9d0c4f < 1d6123102e9fbedc8d25bf4731da6d513173e49e, >= 3.4, >= 3.4 < 6.6.97, >= 6.7 < 6.12.36, >= 6.13 < 6.15.5, 6.16
Fixed versions
6.6.97, 6.12.36, 6.15.5

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416