Daemon crash via incorrect Bluetooth management status
Published Oct 26, 2026 · Updated Oct 26, 2026
Incorrect Bluetooth management replies in Linux allow context-dependent attackers to crash bluetoothd during adapter power-off. In net/bluetooth/mgmt.c, cmd_complete_rsp() passes a command-lookup structure instead of its status field to cmd_status_rsp(), producing an incorrect reply. The observed crash requires pending discovery during shutdown and a client such as bluetoothd 5.72 that mishandles an empty success response; an unauthenticated remote trigger is not established.
Summary
What happened
Incorrect Bluetooth management replies in Linux allow context-dependent attackers to crash bluetoothd during adapter power-off. In net/bluetooth/mgmt.c, cmd_complete_rsp() passes a command-lookup structure instead of its status field to cmd_status_rsp(), producing an incorrect reply. The observed crash requires pending discovery during shutdown and a client such as bluetoothd 5.72 that mishandles an empty success response; an unauthenticated remote trigger is not established.
The record
- CVE
- CVE-2026-99091
- Published
- Oct 26, 2026
- Updated
- Oct 26, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 26, 2026CVE publishedPublication date reported by the CVE source.
- Oct 26, 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=0cc47233af35fb5f10b5e6a027cb4ccd480caf9a
- Affected versionversion=19b40ca62607cef78369549d1af091f2fd558931
- Affected versionversion=4883296505aa7e4863c6869b689afb6005633b23 <44ce36c5789ac84e65de1e98c32db9a5ac04ed47
- Affected versionversion=6.10.14 <6.11
- Affected versionversion=6.1.120 <6.2
- Affected versionversion=6.11.3 <6.12
- Affected versionversion=6.12
- Affected versionversion=6.6.55 <6.6.160
- Affected versionversion=8c3f7943a29145d8a2d8e24893762f7673323eae
- Affected versionversion=f53e1c9c726d83092167f2226f32bd3b73f26c21 <07976405a3c71253e50533ee7b7a8b0dc16ab6ba
- Affected versionversion=f53e1c9c726d83092167f2226f32bd3b73f26c21 <7ed7e038b520cf0dfa12d61c2caddb95e2f6922d
- Affected versionversion=f53e1c9c726d83092167f2226f32bd3b73f26c21 <86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc
- Affected versionversion=f53e1c9c726d83092167f2226f32bd3b73f26c21 <ec227cddd13cd7ac9077d263a73473ac370a055d
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