# CVE-2025-71082: Bluetooth: btusb: revert use of devm_kzalloc in btusb

> A use-after-free vulnerability in the Linux kernel's Bluetooth USB driver allows attackers to cause denial of service or execute arbitrary code.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2025-71082, DEBIAN-CVE-2025-71082, GHSA-68q4-f7q5-5mv5, ROOT-OS-DEBIAN-11-CVE-2025-71082, ROOT-OS-UBUNTU-2204-CVE-2025-71082, ROOT-OS-UBUNTU-2404-CVE-2025-71082, UBUNTU-CVE-2025-71082

## What is CVE-2025-71082?

CVE-2025-71082 is a high-severity use after free vulnerability in Linux kernel, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2025-71082?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-71082?

Apply the vendor's patch.

## Is CVE-2025-71082 being exploited?

There is no known exploitation of CVE-2025-71082 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71082 and fix it if it is affected.

What it is: CVE-2025-71082 is a high-severity use after free vulnerability in Linux kernel, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-71082 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-71082/ (Markdown: https://insights.sbomify.com/CVE-2025-71082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-71082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-71082
- OSV: https://osv.dev/vulnerability/CVE-2025-71082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-71082/
Summaries are generated and may contain mistakes; the official description above is the record.