Kernel use-after-free via L2CAP listener race
Published Sep 17, 2026 · Updated Sep 18, 2026
Use-after-free in Linux Bluetooth L2CAP in affected kernel branches allows local users to trigger unsafe access to freed kernel memory. The l2cap_sock_new_connection_cb function can enqueue a new socket after l2cap_sock_teardown_cb closes and destroys the listening parent because channel state is read without consistent locking. Concurrent listener teardown and L2CAP connection creation are required; the published record does not specify whether the dangling parent access causes a crash, data exposure, or code execution.
Summary
What happened
Use-after-free in Linux Bluetooth L2CAP in affected kernel branches allows local users to trigger unsafe access to freed kernel memory. The l2cap_sock_new_connection_cb function can enqueue a new socket after l2cap_sock_teardown_cb closes and destroys the listening parent because channel state is read without consistent locking. Concurrent listener teardown and L2CAP connection creation are required; the published record does not specify whether the dangling parent access causes a crash, data exposure, or code execution.
The record
- CVE
- CVE-2026-90092
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 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=0c17c8832562b2aac288e89cefd0f46074f54bcb <bf61a65c6093970e3b50031c4b79ebf3bd411eba
- Affected versionversion=1810e42ff6716f320c7269d5850eca48b07b7427 <87276dc15b559d32757a43b4415c8445fbae06c4
- Affected versionversion=1b1c0da227bf63479bac9982fc8d12df9aaea0fb
- Affected versionversion=2ff1a41a912de8517b4482e946dd951b7d80edbf <c47339e169bf4a0a4cfabb91351471f67744c2bc
- Affected versionversion=2ff1a41a912de8517b4482e946dd951b7d80edbf <d4bfa78fd67929b62b02013c107973e0c5b7aa9a
- Affected versionversion=5.10.258 <5.11
- Affected versionversion=5105f3e6b2df619c635b5f6a49fac131a36c7952 <491e4c60017969b053888029998d2a61f298986a
- Affected versionversion=5.15.209 <5.16
- Affected versionversion=6.1.175 <6.1.188
- Affected versionversion=6.12.88 <6.12.110
- Affected versionversion=6.18.30 <6.18.52
- Affected versionversion=6.6.140 <6.6.157
- Affected versionversion=7.0.7 <7.1
- Affected versionversion=7.1
- Affected versionversion=85426e97dc72f2088ba6d27e74cd58c3fbd43e31
- Affected versionversion=a2dcf1a61d056aef15b63c6eae9441344d624389
- Affected versionversion=c88c185ae0a1067823661b220aeea613df2c127b <2a3a27aaf19bf069720e024ce6fde54e6bf80df9
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
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started