Memory corruption via unlocked L2CAP channel removal
Published Jul 2, 2026 · Updated Jul 2, 2026
Improper locking in Linux Kernel allows remote attackers to corrupt kernel memory through nearby Bluetooth L2CAP traffic. cleanup_listen() calls l2cap_chan_close() without conn->lock, allowing concurrent removal from conn->chan_l during connection teardown. Bluetooth and a listening L2CAP service must be present; no OS account or user action is required, and exploitation can panic the kernel.
Summary
What happened
Improper locking in Linux Kernel allows remote attackers to corrupt kernel memory through nearby Bluetooth L2CAP traffic. cleanup_listen() calls l2cap_chan_close() without conn->lock, allowing concurrent removal from conn->chan_l during connection teardown. Bluetooth and a listening L2CAP service must be present; no OS account or user action is required, and exploitation can panic the kernel.
The record
- CVE
- CVE-2026-53358
- Published
- Jul 2, 2026
- Updated
- Jul 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-667, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 2, 2026CVE publishedPublication date reported by the CVE source.
- Jul 2, 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=3.4
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <3634cbdc2eb414b69ffa752ddbe5e0458518e321
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <50dfec218808b148ab4247b1858031b7a32015c5
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <7555fd885a0603f50e49a655850a1f2bd8a25398
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <859d3ace791ed878ae9ba5522c7844d960da8f88
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <89dec92041717b027216e110599e4f6d6c921b79
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <8c8e620467a7b51562dbcefbd1f09f288d7d710d
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <deb8493a8fa599f6c95e2465b12bfdfb7f94a1d9
- Affected versionversion=3df91ea20e744344100b10ae69a17211fcf5b207 <e1c100e2d61bd8c718b7d91fe3e050780a9bf72d
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.
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