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

CVE-2025-71082

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: revert use of devm_kzalloc in btusb This reverts commit 98921dbd00c4e ("Bluetooth: Use devm_kzalloc in btusb.c file"). In btusb_probe(), we use devm_kzalloc() to allocate the btusb data. This ties the lifetime of all the btusb data to the binding of a driver to one interface, INTF. In a driver that binds to other interfaces, ISOC and DIAG, this is an accident waiting to happen. The issue is revealed in btusb_disconnect(), where calling usb_driver_release_interface(&btusb_driver, data->intf) will have devm...

CVSS
7.8
EPSS
0.12%
2.17% percentile
CISA KEV
Not listed
Published
2026.01.14
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: revert use of devm_kzalloc in btusb This reverts commit 98921dbd00c4e ("Bluetooth: Use devm_kzalloc in btusb.c file"). In btusb_probe(), we use devm_kzalloc() to allocate the btusb data. This ties the lifetime of all the btusb data to the binding of a driver to one interface, INTF. In a driver that binds to other interfaces, ISOC and DIAG, this is an accident waiting to happen. The issue is revealed in btusb_disconnect(), where calling usb_driver_release_interface(&btusb_driver, data->intf) will have devm...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < fff9206b0907252a41eb12b7c1407b9347df18b1, >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < cca0e9206e3bcc63cd3e72193e60149165d493cc, >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < c0ecb3e4451fe94f4315e6d09c4046dfbc42090b, >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < 1e54c19eaf84ba652c4e376571093e58e144b339, >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < fdf7c640fb8a44a59b0671143d8c2f738bc48003, >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < 252714f1e8bdd542025b16321c790458014d6880, >= 3.7, >= 3.7.1 < 5.15.198, >= 5.16 < 6.1.160, >= 6.2 < 6.6.120, >= 6.7 < 6.12.64, >= 6.13 < 6.18.4, 3.7, 6.19
Fixed versions
5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4

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
Not available