VulnerabilityPublished 25 Jul 2026

CVE-2026-64471: Linux kernel · Bluetooth: btusb: fix use-after-free on registration failure

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-h76x-2h2r-8jw4

What to do

AI-suggested

A fix has been implemented in the Linux kernel to properly release sibling interfaces on controller registration failure in the btusb driver. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed here; check the Linux kernel vendor advisory or source repository for the specific fixed versions and apply updates accordingly.

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.

Impact

The vulnerability could lead to memory corruption issues such as use-after-free or double-free in the Bluetooth USB driver, potentially causing system instability or crashes. No known exploits in the wild have been reported. The impact is limited to affected Linux kernel versions with the vulnerable btusb driver code path.

Summary

The Linux kernel's Bluetooth USB driver (btusb) contained a use-after-free vulnerability triggered by failure to release sibling interfaces when controller registration failed. This could cause use-after-free and double-free errors when the interfaces were later disconnected. The vulnerability was addressed by ensuring sibling interfaces are properly released during error handling in the probe function, preventing memory corruption.

References

Community reviews

Loading reviews…