Review reviewHigh

CVE-2025-40283

Linux

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: reorder cleanup in btusb_disconnect to avoid UAF There is a KASAN: slab-use-after-free read in btusb_disconnect(). Calling "usb_driver_release_interface(&btusb_driver, data->intf)" will free the btusb data associated with the interface. The same data is then used later in the function, hence the UAF. Fix by moving the accesses to btusb data to before the data is free'd.

CVSS
7.8
EPSS
0.14%
3.79% percentile
CISA KEV
Not listed
Published
2025.12.07
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: btusb: reorder cleanup in btusb_disconnect to avoid UAF There is a KASAN: slab-use-after-free read in btusb_disconnect(). Calling "usb_driver_release_interface(&btusb_driver, data->intf)" will free the btusb data associated with the interface. The same data is then used later in the function, hence the UAF. Fix by moving the accesses to btusb data to before the data is free'd.

Affected product and versions

Product
Linux
Affected versions
>= fd913ef7ce619467c6b0644af48ba1fec499c623 < 297dbf87989e09af98f81f2bcb938041785557e8, >= fd913ef7ce619467c6b0644af48ba1fec499c623 < f858f004bc343a7ae9f2533bbb2a3ab27428532f, >= fd913ef7ce619467c6b0644af48ba1fec499c623 < 7a6d1e740220ff9dfcb6a8c994d6ba49e76db198, >= fd913ef7ce619467c6b0644af48ba1fec499c623 < 5dc00065a0496c36694afe11e52a5bc64524a9b8, >= fd913ef7ce619467c6b0644af48ba1fec499c623 < 1c28c1e1522c773a94e26950ffb145e88cd9834b, >= fd913ef7ce619467c6b0644af48ba1fec499c623 < 95b9b98c93b1c0916a3d4cf4540b7f5d69145a0d, >= fd913ef7ce619467c6b0644af48ba1fec499c623 < a2610ecd9fd5708be8997ca8f033e4200c0bb6af, >= fd913ef7ce619467c6b0644af48ba1fec499c623 < 23d22f2f71768034d6ef86168213843fc49bf550, >= 4.11
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux 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
Not available