CVEvulnerability
CVE-2025-71082
7.8 HIGH
Official page ↗
- Status
- Modified
- Published
- 2026-01-13
- Last modified
- 2026-10-19
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 ([email protected])
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-416
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 configurations
• linux linux kernel (>= 3.7.1 < 5.15.198)
• linux linux kernel (>= 5.16 < 6.1.160)
• linux linux kernel (>= 6.2 < 6.6.120)
• linux linux kernel (>= 6.7 < 6.12.64)
• linux linux kernel (>= 6.13 < 6.18.4)
• linux linux kernel 3.7
• linux linux kernel 6.19
Related
Weakness · CWE (1)
- CWE-416 Use After Free weakness
References
- https://git.kernel.org/stable/c/1e54c19eaf84ba652c4e376571093e58e144b339 Patch
- https://git.kernel.org/stable/c/252714f1e8bdd542025b16321c790458014d6880 Patch
- https://git.kernel.org/stable/c/c0ecb3e4451fe94f4315e6d09c4046dfbc42090b Patch
- https://git.kernel.org/stable/c/cca0e9206e3bcc63cd3e72193e60149165d493cc Patch
- https://git.kernel.org/stable/c/fdf7c640fb8a44a59b0671143d8c2f738bc48003 Patch
- https://git.kernel.org/stable/c/fff9206b0907252a41eb12b7c1407b9347df18b1 Patch