Kernel compromise via L2CAP connection use-after-free
Published Oct 21, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux kernel Bluetooth L2CAP stack allows remote attackers within Bluetooth range to crash the kernel. The l2cap_connect_req path dereferences an l2cap_conn after a concurrent connection abort frees it; the fix moves management notification before L2CAP processing under the HCI device lock. An unauthenticated, unpaired BR/EDR peer can control the request-and-teardown race, resulting in kernel memory disclosure, corruption, control-flow hijacking, or a panic.
Summary
What happened
Use-after-free in the Linux kernel Bluetooth L2CAP stack allows remote attackers within Bluetooth range to crash the kernel. The l2cap_connect_req path dereferences an l2cap_conn after a concurrent connection abort frees it; the fix moves management notification before L2CAP processing under the HCI device lock. An unauthenticated, unpaired BR/EDR peer can control the request-and-teardown race, resulting in kernel memory disclosure, corruption, control-flow hijacking, or a panic.
The record
- CVE
- CVE-2024-49950
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.8
- Affected versionversion=7b064edae38d62d8587a8c574f93b53ce75ae749 <333b4fd11e89b29c84c269123f871883a30be586
- Affected versionversion=7b064edae38d62d8587a8c574f93b53ce75ae749 <686e05c9dbd68766c6bda5f31f7e077f36a7fb29
- Affected versionversion=7b064edae38d62d8587a8c574f93b53ce75ae749 <78d30ce16fdf9c301bcd8b83ce613cea079cea83
- Affected versionversion=7b064edae38d62d8587a8c574f93b53ce75ae749 <a1c6174e23df10b8e5770e82d63bc6e2118a3dc7
- Affected versionversion=7b064edae38d62d8587a8c574f93b53ce75ae749 <b22346eec479a30bfa4a02ad2c551b54809694d0
- Affected versionversion=7b064edae38d62d8587a8c574f93b53ce75ae749 <b90907696c30172b809aa3dd2f0caffae761e4c6
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