Kernel memory corruption via duplicate channel linkage
Published Nov 2, 2026 · Updated Nov 2, 2026
Linux Bluetooth L2CAP has a race allowing local users to corrupt kernel memory via concurrent socket bind and connect calls. l2cap_sock_bind() overwrites channel state without the channel lock, allowing a later connect() to call __l2cap_chan_add() again and link an already attached channel. Exploitation requires local L2CAP socket access in the initial network namespace, not a radio peer; corrupted linkage supplies kernel read/write and control-flow primitives or causes hangs and crashes.
Summary
What happened
Linux Bluetooth L2CAP has a race allowing local users to corrupt kernel memory via concurrent socket bind and connect calls. l2cap_sock_bind() overwrites channel state without the channel lock, allowing a later connect() to call __l2cap_chan_add() again and link an already attached channel. Exploitation requires local L2CAP socket access in the initial network namespace, not a radio peer; corrupted linkage supplies kernel read/write and control-flow primitives or causes hangs and crashes.
The record
- CVE
- CVE-2026-99239
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 2, 2026CVE publishedPublication date reported by the CVE source.
- Nov 2, 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=0b0e2bf39cf99e458d991b9df253727e036a7d7d <52fe88e4ef87311eee32b45c65603e7c69e75e7d
- Affected versionversion=32d783cafb46ff3ca58e6f9fd62c9c5f35eaf26b <820579652b24ce277e0097cd65b42bd9b7b8bf07
- Affected versionversion=50c38d9f42a529691e4e67ea9cedf4f0bfc8d277
- Affected versionversion=5.10.265 <5.10.273
- Affected versionversion=5.15.216 <5.15.224
- Affected versionversion=6.1.183 <6.1.191
- Affected versionversion=6.12.97 <6.12.115
- Affected versionversion=6.18.39 <6.18.60
- Affected versionversion=6.6.145 <6.6.161
- Affected versionversion=7.1.4 <7.2
- Affected versionversion=7.2
- Affected versionversion=8922c7940bae9ce4b1736dddb6362370793835c2 <e618d928ec7f88cbeadfa3542adcac40f474e629
- Affected versionversion=8f90405a4a6f1f1880dc07996b47bf57c712bd8a <85cc289eb08afa975375f838187369e68b429ee0
- Affected versionversion=91047a4396a8b1857a6f712a90cf33ec0012b189 <fabaff1c59ff2cc89cb7e5bd0186a5e15f0c73b2
- Affected versionversion=b66774b48dd98f07254951f74ea6f513efe7ff8b <73820561d8cbfd3364a29b8fa77f1707f26029da
- Affected versionversion=b66774b48dd98f07254951f74ea6f513efe7ff8b <d3afd7803f9bc2a8c4270199497b60158b2fc647
- Affected versionversion=d3b739db5dc6f688a60d56da872fabaf65246032 <10c705dd706aa93164ba41f2566f15206d6c178e
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us