Bluetooth hang via RFCOMM lock-order inversion
Published Oct 23, 2026 · Updated Oct 23, 2026
Deadlock in Linux Bluetooth RFCOMM allows local users to hang Bluetooth processing via a socket connection during link authentication. The rfcomm_dlc_open() path acquires rfcomm_mutex before hdev->lock, while rfcomm_security_cfm() acquires them in the opposite order. The condition requires overlapping RFCOMM connection and BR/EDR authentication activity; an incoming Bluetooth connection alone does not establish both lock orders.
Summary
What happened
Deadlock in Linux Bluetooth RFCOMM allows local users to hang Bluetooth processing via a socket connection during link authentication. The rfcomm_dlc_open() path acquires rfcomm_mutex before hdev->lock, while rfcomm_security_cfm() acquires them in the opposite order. The condition requires overlapping RFCOMM connection and BR/EDR authentication activity; an incoming Bluetooth connection alone does not establish both lock orders.
The record
- CVE
- CVE-2026-99009
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=1b7841ffad08e911e8c4b9470f3fa08423568940 <d2206e8c78be69d21d4f5343c3e99fbaeef41cbb
- Affected versionversion=3873f3449701b3dc98cba577923be6493598e7a1
- Affected versionversion=5.10.270 <5.11
- Affected versionversion=5.15.221 <5.16
- Affected versionversion=6.1.188 <6.2
- Affected versionversion=6.12.109 <6.12.114
- Affected versionversion=6.18.50 <6.18.58
- Affected versionversion=62ce8b33eb238cf18c15207332fbdc26d858f592
- Affected versionversion=6.6.157 <6.6.160
- Affected versionversion=7.2.4 <7.2.11
- Affected versionversion=759c185d0bbdb131357408f50b8735e04ed3caff <ac022970e9fb0a5f7e7d1f6c8e104c1ed924dd1c
- Affected versionversion=7ded3264106418c6456ccceaafd9fda596ce12c3
- Affected versionversion=82425b14f0fb22e46cfddc56d6465570f5ed0ce6 <4dc3d5a004b8fd59f3c905631dbb18cb601b1b41
- Affected versionversion=946d76db77ee5f922968ce558629ae47b381e3fc <cc7732b8549ecb6f02457edeb8db1f6d255e381c
- Affected versionversion=fbf7961964a6e93360179f64712320ae9a1e9577 <f492de11b325446b0b11bc2eb86e1f546eaa61b6
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Contact us