Bluetooth channel teardown via stale L2CAP identifier
Published Jul 19, 2026 · Updated Jul 19, 2026
State-management flaw in Linux Kernel 5.7 through 7.0.11 allows physically proximate attackers to tear down Bluetooth L2CAP channels. l2cap_ecred_reconf_rsp() returns after a successful ECRED reconfiguration without clearing chan->ident, so a replayed failure response matches the live channel and passes it to l2cap_chan_del(). The attacker must establish a Bluetooth Low Energy ACL connection and complete reconfiguration; repeated replays interrupt Bluetooth service, while concurrent teardown can expose a kernel use-after-free.
Summary
What happened
State-management flaw in Linux Kernel 5.7 through 7.0.11 allows physically proximate attackers to tear down Bluetooth L2CAP channels. l2cap_ecred_reconf_rsp() returns after a successful ECRED reconfiguration without clearing chan->ident, so a replayed failure response matches the live channel and passes it to l2cap_chan_del(). The attacker must establish a Bluetooth Low Energy ACL connection and complete reconfiguration; repeated replays interrupt Bluetooth service, while concurrent teardown can expose a kernel use-after-free.
The record
- CVE
- CVE-2026-63976
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=15f02b91056253e8cdc592888f431da0731337b8 <00e1950716c6ed67d74777b2db286b0fa23b4be9
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <3b5b5f423b4fd23404a393bda8adba3cd6f74ef1
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <59f5ecf6ad5c4db6ae81965a96156954a3b0d89a
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <8e7977afaef37c6bd2b2654f1bce6ab40d471147
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <ae0152d77d101c920769934fb102b18de0c6f526
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <c2afd2613fda90107c5e2fe8e855627451749c78
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <cc2b4f749de09975bfa06e58bbbad2f6acd4c79c
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <f39049304ba655ffcbb92edbdf8c51a1f1210bed
- Affected versionversion=5.7
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
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