CVE-2026-98290: Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
Published Oct 6, 2026
·Updated
Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup
Affected Software
1 affected component
Linux Linux kernel
Event History
Oct 6, 2026
CVE Published
via MITRE·08:45 AM
Data Sourced
via MITRE·08:45 AM
DescriptionSeverity
Data Sourced
via NVD·09:18 AM
DescriptionSeverity
Oct 7, 2026
Data Sourced
via Microsoft·08:28 AM
DescriptionSeverityWeakness
Frequently Asked Questions
1
Which deployments are most relevant to this issue?
Linux systems using Bluetooth RFCOMM listening sockets are the relevant population. The affected cleanup path involves listener shutdown while unaccepted child sockets are present or being added.
2
What access would an attacker need?
The CVSS vector indicates adjacent-network access, with no privileges or user interaction required. Exploitation has high attack complexity and would depend on timing around RFCOMM connection handling and listener cleanup.
3
How can administrators identify the condition?
The described issue is reported by lockdep as a possible deadlock caused by reverse lock ordering between listener cleanup and the RFCOMM worker. Systems with lockdep enabled may therefore log the relevant warning during RFCOMM connection or DLC state activity.