Memory corruption via unreleased btusb sibling interfaces
Published Jul 25, 2026 · Updated Jul 25, 2026
Use-after-free in Linux Kernel btusb since 2.6.27 allows attackers to trigger invalid memory access after registration failure. The btusb_probe error path frees the HCI device without clearing or releasing claimed diagnostic and isochronous sibling USB interfaces. Controller registration must fail and a sibling interface must later disconnect; the record does not establish how attackers can force these conditions.
Summary
What happened
Use-after-free in Linux Kernel btusb since 2.6.27 allows attackers to trigger invalid memory access after registration failure. The btusb_probe error path frees the HCI device without clearing or releasing claimed diagnostic and isochronous sibling USB interfaces. Controller registration must fail and a sibling interface must later disconnect; the record does not establish how attackers can force these conditions.
The record
- CVE
- CVE-2026-64471
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.27
- Affected versionversion=9bfa35fe422c74882e27cc54450a5f76c96aad68 <14e02f1449ba425a44dedbec9a21efafb056e09f
- Affected versionversion=9bfa35fe422c74882e27cc54450a5f76c96aad68 <1ce5012944afaddbda939ec6bae9800fce84abbc
- Affected versionversion=9bfa35fe422c74882e27cc54450a5f76c96aad68 <468fcdfaeb937163dd250773a9fed17ab1fa203c
- Affected versionversion=9bfa35fe422c74882e27cc54450a5f76c96aad68 <8db0ce3de78367f61c2970c0f16d9adee8830a23
- Affected versionversion=9bfa35fe422c74882e27cc54450a5f76c96aad68 <da7d7758fe884b256ddc9fef562e5ddef7952383
- Affected versionversion=9bfa35fe422c74882e27cc54450a5f76c96aad68 <e09ac7d0c6859a360bf36e7104aef03f88184e0b
- Affected versionversion=9bfa35fe422c74882e27cc54450a5f76c96aad68 <e6313b800da61a26c2fdd5eba0105e197c0ab3bc
- Affected versionversion=9bfa35fe422c74882e27cc54450a5f76c96aad68 <eedc6867ebad73edbfaf9a0a65fbef7115cc4753
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo