CVE-2025-71082

Summary

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 free the data that is also being used by the other interfaces of the driver that may not be released yet. To fix this, revert the use of devm and go back to freeing memory explicitly.

Impact & exploitability

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

Affected products we track (1)

Recommendation

Apply the vendor fix promptly. Open any affected product above for its exact safe version.

Official patch: https://git.kernel.org/stable/c/1e54c19eaf84ba652c4e376571093e58e144b339 ↗

Additional information

• NVD record
• https://git.kernel.org/stable/c/1e54c19eaf84ba652c4e376571093e58e144b339Patch
• https://git.kernel.org/stable/c/252714f1e8bdd542025b16321c790458014d6880Patch
• https://git.kernel.org/stable/c/c0ecb3e4451fe94f4315e6d09c4046dfbc42090bPatch
• https://git.kernel.org/stable/c/cca0e9206e3bcc63cd3e72193e60149165d493ccPatch
• https://git.kernel.org/stable/c/fdf7c640fb8a44a59b0671143d8c2f738bc48003Patch
• https://git.kernel.org/stable/c/fff9206b0907252a41eb12b7c1407b9347df18b1Patch