Back

HIGH

Bluetooth: btusb: revert use of devm_kzalloc in btusb

Published Jan 13, 2026

Description

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

Remediation

Red Hat statement

This affects systems with USB Bluetooth adapters. The issue occurs during Bluetooth disconnect operations when multiple interfaces are involved. The fix reverts to explicit memory management to properly handle multi-interface lifetimes.

Metrics

Weaknesses (1)

References (11)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner Linux
Published Jan 13, 2026
Updated Aug 5, 2026
Reserved Jan 13, 2026
CISA Vulnrichment
Updated Jun 10, 2026
NVD
Status Modified
Modified Jul 30, 2026
Red Hat
Severity Low
Public date Jan 13, 2026