Kernel compromise via L2CAP channel use-after-free
Published Sep 18, 2025 · Updated Sep 18, 2025
Use-after-free in Bluetooth L2CAP in affected Linux kernel releases allows attackers to compromise the kernel via Bluetooth proximity. l2cap_connect_create_rsp obtains an l2cap_chan pointer without first retaining it, so concurrent channel teardown can free the object before the response path locks it. An unauthenticated Bluetooth peer within radio range can control the signaling and teardown race, leading to kernel memory disclosure, corruption, control-flow hijacking, or panic.
Summary
What happened
Use-after-free in Bluetooth L2CAP in affected Linux kernel releases allows attackers to compromise the kernel via Bluetooth proximity. l2cap_connect_create_rsp obtains an l2cap_chan pointer without first retaining it, so concurrent channel teardown can free the object before the response path locks it. An unauthenticated Bluetooth peer within radio range can control the signaling and teardown race, leading to kernel memory disclosure, corruption, control-flow hijacking, or panic.
The record
- CVE
- CVE-2022-50386
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0c108cf3ad386e0084277093b55a351c49e0be27
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <11e40d6c0823f699d8ad501e48d1c3ae4be386cd
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <15fc21695eb606bdc5d483b92118ee42610a952d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <35fcbc4243aad7e7d020b7c1dfb14bb888b20a4f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6ffde6e03085874ae22263ff4cef4869f797e84f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7d6f9cb24d2b2f6b6370eac074e2e6b1bafdad45
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <843fc4e386dd84b806a7f07fb062d8c3a44e5364
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d1e894f950ad48897d1a7cb05909ea29d8c3810e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d91fc2836562f299f34e361e089e9fe154da4f73
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