Answer in brief
CVE-2026-99091 records a Unknown severity vulnerability in Bluetooth: MGMT: Fix status of pending commands flushed on power off. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4883296505aa7e4863c6869b689afb6005633b23 <44ce36c5789ac84e65de1e98c32db9a5ac04ed47 || >=f53e1c9c726d83092167f2226f32bd3b73f26c21 <7ed7e038b520cf0dfa12d61c2caddb95e2f6922d || >=f53e1c9c726d83092167f2226f32bd3b73f26c21 <ec227cddd13cd7ac9077d263a73473ac370a055d || >=f53e1c9c726d83092167f2226f32bd3b73f26c21 <07976405a3c71253e50533ee7b7a8b0dc16ab6ba || >=f53e1c9c726d83092167f2226f32bd3b73f26c21 <86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc || 19b40ca62607cef78369549d1af091f2fd558931 || 0cc47233af35fb5f10b5e6a027cb4ccd480caf9a || 8c3f7943a29145d8a2d8e24893762f7673323eae || >=6.6.55 <6.6.160 || >=6.1.120 <6.2 || >=6.10.14 <6.11 || >=6.11.3 <6.12 | 44ce36c5789ac84e65de1e98c32db9a5ac04ed47, 7ed7e038b520cf0dfa12d61c2caddb95e2f6922d, ec227cddd13cd7ac9077d263a73473ac370a055d, 07976405a3c71253e50533ee7b7a8b0dc16ab6ba, 86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc, 6.6.160, 6.2, 6.11, 6.12 |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Oct 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 26, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix status of pending commands flushed on power off cmd_complete_rsp() receives a struct cmd_lookup and, for a pending command that has no cmd_complete callback, falls through to cmd_status_rsp(cmd, data). cmd_status_rsp() reads data as a u8 *, so the status sent comes from the first byte of match->sk's representation, not from match->mgmt_status. commit f53e1c9c726d ("Bluetooth: MGMT: Fix possible crash on mgmt_index_removed") changed the callers' data from &status to &match and updated the cmd_complete branch to match->mgmt_status, but left the fall-through passing data unchanged. In mgmt_index_removed() match->sk is NULL, so every such command is answered with status 0x00 (Success) instead of MGMT_STATUS_INVALID_INDEX. In __mgmt_power_off() it is NULL too, unless a Set Powered command was pending: then settings_rsp() has stored that command's socket in match->sk, and the byte sent comes from the socket pointer. Either way the status the caller set, MGMT_STATUS_NOT_POWERED (or MGMT_STATUS_INVALID_INDEX when the device is being unregistered), is lost. Pass the status the callers set. This was seen on a QCA9377 laptop: bluetoothd's Start Discovery, pending when the adapter was powered off, was answered with Command Status 0x00 and no parameters, and bluetoothd 5.72 crashed on the zero-length success. BlueZ master has since added the length check on that path ("adapter: Fix crash on short start discovery reply", BlueZ a734b06059cb), but userspace should still be told Not Powered, not Success. Tested on Ubuntu 7.0.0-31 with a virtual controller (hci_vhci): power off is held in HCI Write Scan Enable while a Start Discovery is submitted, and the flush answers it with status 0x00 before this change and 0x0f (Not Powered) after.
Quoted source text, attributed separately from HOL analysis.