Kernel warning via uninitialized Bluetooth mutex
Published Sep 25, 2026 · Updated Sep 25, 2026
Race condition in the Linux Bluetooth HCI core allows attackers to trigger a kernel lock-debugging warning during device registration. hci_register_dev queues power_on before adv_monitors_idr and the MSFT extension are initialized, while msft_register exposes msft_data before initializing filter_lock. A device with HCI_QUIRK_RAW_DEVICE can let hci_power_on call msft_do_close concurrently, causing mutex_lock to use the uninitialized mutex; only the warning is confirmed.
Summary
What happened
Race condition in the Linux Bluetooth HCI core allows attackers to trigger a kernel lock-debugging warning during device registration. hci_register_dev queues power_on before adv_monitors_idr and the MSFT extension are initialized, while msft_register exposes msft_data before initializing filter_lock. A device with HCI_QUIRK_RAW_DEVICE can let hci_power_on call msft_do_close concurrently, causing mutex_lock to use the uninitialized mutex; only the warning is confirmed.
The record
- CVE
- CVE-2026-98109
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 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=6.4.16 <6.5
- Affected versionversion=6.5.3 <6.6
- Affected versionversion=6.6
- Affected versionversion=80fe27811c56ecd3896c3d511ab8298146071d98
- Affected versionversion=9e14606d8f38ea52a38c27692a9c1513c987a5da <57938bbdb9bf7fd41cbd5cd509ec10c4b22bec18
- Affected versionversion=9e14606d8f38ea52a38c27692a9c1513c987a5da <a11ebe8dc0333fb870bbbb656b34690e87ee3f98
- Affected versionversion=9e14606d8f38ea52a38c27692a9c1513c987a5da <b1faf348c29e6f8302ec7769cbf1c1ef05be014f
- Affected versionversion=9e14606d8f38ea52a38c27692a9c1513c987a5da <d427b1c71d9798083e954d3c13469dc0a2305868
- Affected versionversion=f9965f7f38c90449a5fb26edb8a7d22b1dcf0283
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.
Get started