Adjacent kernel crash via unlocked channel deletion
Published Jun 24, 2026 · Updated Jun 24, 2026
Improper locking in Linux Kernel 5.7 and later allows physically proximate attackers to crash the kernel via a crafted BLE response. The l2cap_ecred_reconf_rsp() handler calls l2cap_chan_del() without l2cap_chan_lock(), allowing deletion to corrupt the channel list during concurrent iteration. A nearby BLE peer must reach an established ECRED channel and win the race; reported consequences are a kernel crash or corrupted connection state.
Summary
What happened
Improper locking in Linux Kernel 5.7 and later allows physically proximate attackers to crash the kernel via a crafted BLE response. The l2cap_ecred_reconf_rsp() handler calls l2cap_chan_del() without l2cap_chan_lock(), allowing deletion to corrupt the channel list during concurrent iteration. A nearby BLE peer must reach an established ECRED channel and win the race; reported consequences are a kernel crash or corrupted connection state.
The record
- CVE
- CVE-2026-53071
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, CWE-667, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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 <0ccd75c51f620374086f359e906917676e699a1c
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <330b20ec97916961ee0e6c29c06bc0fa7c96e64c
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <42776497cdbc9a665b384a6dcb85f0d4bd927eab
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <5501d055a1ce3c747141e3955ba8cf034d193f3e
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <77a853aec710b2fdf41fa298ea3cbc9a4358f917
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <96dca51715d86559ed6ed8028e5445cecb80f3ae
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <dc89961b76f12aff47124c1df4bdb32a080f4d0c
- Affected versionversion=15f02b91056253e8cdc592888f431da0731337b8 <fe1188abdae9b7a8199dcdfcf9244d5e5d61eb14
- 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