Description
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.
Affected products
linux: linux kernel
References6
- git.kernel.org/stable/c/1e54c19eaf84ba652c4e376571093e58e144b339 Patch
- git.kernel.org/stable/c/252714f1e8bdd542025b16321c790458014d6880 Patch
- git.kernel.org/stable/c/c0ecb3e4451fe94f4315e6d09c4046dfbc42090b Patch
- git.kernel.org/stable/c/cca0e9206e3bcc63cd3e72193e60149165d493cc Patch
- git.kernel.org/stable/c/fdf7c640fb8a44a59b0671143d8c2f738bc48003 Patch
- git.kernel.org/stable/c/fff9206b0907252a41eb12b7c1407b9347df18b1 Patch
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 4 · as of 12 November 2026
- CWE
- CWE-416
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.