# CVE-2026-64471: Bluetooth: btusb: fix use-after-free on registration failure

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

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** AZL-93449, BELL-CVE-2026-64471, DEBIAN-CVE-2026-64471, GHSA-h76x-2h2r-8jw4, ROOT-OS-UBUNTU-2204-CVE-2026-64471, UBUNTU-CVE-2026-64471

## What is CVE-2026-64471?

CVE-2026-64471 is an use after free vulnerability in Linux, published on 25 Jul 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: fix use-after-free on registration failure

Make sure to release the sibling interfaces in case controller
registration fails to avoid use-after-free and double-free when they are
eventually disconnected.

This issue was reported by Sashiko while reviewing a fix for a wakeup
source leak in the btusb probe errors paths.

## Which versions are affected by CVE-2026-64471?


## How do I fix CVE-2026-64471?

Apply the vendor's patch.

## Is CVE-2026-64471 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64471 and fix it if it is affected.

What it is: CVE-2026-64471 is an use after free vulnerability in Linux, published on 25 Jul 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-2026-64471 in the wild and no public exploit code.

Affected product: Linux. 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-2026-64471/ (Markdown: https://insights.sbomify.com/CVE-2026-64471/index.md)
```

## Sources

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

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