Use-after-free via dangling L2CAP socket pointer
Published Dec 27, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux kernel Bluetooth L2CAP stack since 3.6 allows local users to trigger a dangling pointer during socket creation. On an allocation error, l2cap_sock_alloc() frees the socket object but leaves the freed sk pointer attached to the caller-supplied sock object. Exploitation requires local low-privileged access and a failing allocation; Ubuntu reports that sock->ops is NULL and the dangling pointer is never dereferenced.
Summary
What happened
Use-after-free in the Linux kernel Bluetooth L2CAP stack since 3.6 allows local users to trigger a dangling pointer during socket creation. On an allocation error, l2cap_sock_alloc() frees the socket object but leaves the freed sk pointer attached to the caller-supplied sock object. Exploitation requires local low-privileged access and a failing allocation; Ubuntu reports that sock->ops is NULL and the dangling pointer is never dereferenced.
The record
- CVE
- CVE-2024-56605
- Published
- Dec 27, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 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.6
- Affected versionversion=49dfbb9129c4edb318578de35cc45c555df37884 <61686abc2f3c2c67822aa23ce6f160467ec83d35
- Affected versionversion=49dfbb9129c4edb318578de35cc45c555df37884 <7c4f78cdb8e7501e9f92d291a7d956591bf73be9
- Affected versionversion=49dfbb9129c4edb318578de35cc45c555df37884 <8ad09ddc63ace3950ac43db6fbfe25b40f589dd6
- Affected versionversion=49dfbb9129c4edb318578de35cc45c555df37884 <a8677028dd5123e5e525b8195483994d87123de4
- Affected versionversion=49dfbb9129c4edb318578de35cc45c555df37884 <bb2f2342a6ddf7c04f9aefbbfe86104cd138e629
- Affected versionversion=49dfbb9129c4edb318578de35cc45c555df37884 <daa13175a6dea312a76099066cb4cbd4fc959a84
- Affected versionversion=49dfbb9129c4edb318578de35cc45c555df37884 <f6ad641646b67f29c7578dcd6c25813c7dcbf51e
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