Kernel compromise via L2CAP receive race
Published May 1, 2025 · Updated Aug 5, 2026
Use-after-free in the Linux kernel Bluetooth L2CAP subsystem allows adjacent attackers to crash or compromise the kernel via crafted traffic. A concurrent userspace receive can dequeue and free an SKB while l2cap_reassemble_sdu callers still read its control block. Reachability requires an active L2CAP ERTM or streaming channel and a socket reader; successful triggering can panic the kernel or enable memory corruption.
Summary
What happened
Use-after-free in the Linux kernel Bluetooth L2CAP subsystem allows adjacent attackers to crash or compromise the kernel via crafted traffic. A concurrent userspace receive can dequeue and free an SKB while l2cap_reassemble_sdu callers still read its control block. Reachability requires an active L2CAP ERTM or streaming channel and a socket reader; successful triggering can panic the kernel or enable memory corruption.
The record
- CVE
- CVE-2022-49910
- Published
- May 1, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2025CVE 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.6
- Affected versionversion=4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 <03af22e23b96fb7ef75fb7885407ef457e8b403d
- Affected versionversion=4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 <3aff8aaca4e36dc8b17eaa011684881a80238966
- Affected versionversion=4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 <4cd094fd5d872862ca278e15b9b51b07e915ef3f
- Affected versionversion=4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 <6c7407bfbeafc80a04e6eaedcf34d378532a04f2
- Affected versionversion=4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 <8278a87bb1eeea94350d675ef961ee5a03341fde
- Affected versionversion=4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 <9a04161244603f502c6e453913e51edd59cb70c1
- Affected versionversion=4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 <cb1c012099ef5904cd468bdb8d6fcdfdd9bcb569
- Affected versionversion=4b51dae96731c9d82f5634e75ac7ffd3b9c1b060 <dc30e05bb18852303084430c03ca76e69257d9ea
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