Kernel memory corruption via L2CAP socket race
Published Jul 29, 2026 · Updated Jul 29, 2026
Use-after-free in the Linux Kernel Bluetooth L2CAP subsystem allows physically proximate attackers to corrupt kernel memory via Bluetooth. l2cap_sock_new_connection_cb() drops the parent lock before returning the child channel, allowing another task to accept and free the exposed child socket before the callback dereferences it. Exploitation requires Bluetooth proximity and a concurrent accept and free of the child socket; the resulting kernel use-after-free permits memory corruption.
Summary
What happened
Use-after-free in the Linux Kernel Bluetooth L2CAP subsystem allows physically proximate attackers to corrupt kernel memory via Bluetooth. l2cap_sock_new_connection_cb() drops the parent lock before returning the child channel, allowing another task to accept and free the exposed child socket before the callback dereferences it. Exploitation requires Bluetooth proximity and a concurrent accept and free of the child socket; the resulting kernel use-after-free permits memory corruption.
The record
- CVE
- CVE-2026-64557
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 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.13
- Affected versionversion=8ffb929098a56939ac71509302eeab5b207bf262 <36da806f7fbaee56ad9e81859deec203f9728700
- Affected versionversion=8ffb929098a56939ac71509302eeab5b207bf262 <6fef032af0092ed5ccb767239a9ac1bc38c08a40
- Affected versionversion=8ffb929098a56939ac71509302eeab5b207bf262 <733e76e74e406c1d1ddc7369420dd8a47f48bb8a
- Affected versionversion=8ffb929098a56939ac71509302eeab5b207bf262 <84e718b6a814edc84159361f9f454a4e92ae91ae
- Affected versionversion=8ffb929098a56939ac71509302eeab5b207bf262 <8c37e4338c801ebb8cee52436c01c41e009f6e87
- Affected versionversion=8ffb929098a56939ac71509302eeab5b207bf262 <b39298044e5534612511a2ff5de03ba5f6e7a820
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
No sourced classifications are available.
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