Potential RFCOMM hang via listener-cleanup lock inversion
Published Oct 6, 2026 · Updated Oct 6, 2026
A lock-order inversion in Linux kernel Bluetooth RFCOMM exposes listener cleanup to a possible service hang during connection handling. The rfcomm_sock_cleanup_listen() path closes queued child sockets while rfcomm_sock_close() holds a child socket lock and rfcomm_dlc_close() requests rfcomm_mutex, opposite the RFCOMM worker's lock order. The risk requires a listening RFCOMM socket with unaccepted children and overlapping cleanup and connection activity; the public reproducer establishes a lockdep warning, not a confirmed system-wide hang.
Summary
What happened
A lock-order inversion in Linux kernel Bluetooth RFCOMM exposes listener cleanup to a possible service hang during connection handling. The rfcomm_sock_cleanup_listen() path closes queued child sockets while rfcomm_sock_close() holds a child socket lock and rfcomm_dlc_close() requests rfcomm_mutex, opposite the RFCOMM worker's lock order. The risk requires a listening RFCOMM socket with unaccepted children and overlapping cleanup and connection activity; the public reproducer establishes a lockdep warning, not a confirmed system-wide hang.
The record
- CVE
- CVE-2026-98290
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 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=5.15
- Affected versionversion=b7ce436a5d798bc59e71797952566608a4b4626b <18174b166547ef41973cc19feb5ef9cab39a8def
- Affected versionversion=b7ce436a5d798bc59e71797952566608a4b4626b <4aafb47301a799d3e01230d6568c4e93524e1523
- Affected versionversion=b7ce436a5d798bc59e71797952566608a4b4626b <801fb950cae7048eb7d83b18857d1ca37b8cd5a4
- Affected versionversion=b7ce436a5d798bc59e71797952566608a4b4626b <bfce253f039eb5f58b810af267942a9f59207254
- Affected versionversion=b7ce436a5d798bc59e71797952566608a4b4626b <c6792c441767256030606eb82dca5d5fc360dd9a
- Affected versionversion=b7ce436a5d798bc59e71797952566608a4b4626b <c741977e413f5b49d306700820fb55ccb8269f5a
- Affected versionversion=b7ce436a5d798bc59e71797952566608a4b4626b <eb4adaa46e4c9e6efa7be3ce06398f4d7c39b57c
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
Public exploit references
- syzbot RFCOMM lock-inversion C reproducerproof of concept · demonstrated
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