{"id":"CVE-2026-99091","title":"Bluetooth: MGMT: Fix status of pending commands flushed on power off","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix status of pending commands flushed on power off\n\ncmd_complete_rsp() receives a struct cmd_lookup and, for a pending\ncommand that has no cmd_complet…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 4883296505aa7e4863c6869b689afb6005633b23 < 44ce36c5789ac84e65de1e98c32db9a5ac04ed47","Linux >= f53e1c9c726d83092167f2226f32bd3b73f26c21 < 7ed7e038b520cf0dfa12d61c2caddb95e2f6922d","Linux >= f53e1c9c726d83092167f2226f32bd3b73f26c21 < ec227cddd13cd7ac9077d263a73473ac370a055d","Linux >= f53e1c9c726d83092167f2226f32bd3b73f26c21 < 07976405a3c71253e50533ee7b7a8b0dc16ab6ba","Linux >= f53e1c9c726d83092167f2226f32bd3b73f26c21 < 86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc","Linux 19b40ca62607cef78369549d1af091f2fd558931","Linux 0cc47233af35fb5f10b5e6a027cb4ccd480caf9a","Linux 8c3f7943a29145d8a2d8e24893762f7673323eae","Linux >= 6.6.55 < 6.6.160","Linux >= 6.1.120 < 6.2","Linux >= 6.10.14 < 6.11","Linux >= 6.11.3 < 6.12","Linux 6.12"],"published":"2026-10-26","updated":"2026-10-26","sourceUpdated":"2026-10-26T14:52:00.262Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-99091","references":[{"url":"https://git.kernel.org/stable/c/44ce36c5789ac84e65de1e98c32db9a5ac04ed47"},{"url":"https://git.kernel.org/stable/c/7ed7e038b520cf0dfa12d61c2caddb95e2f6922d"},{"url":"https://git.kernel.org/stable/c/ec227cddd13cd7ac9077d263a73473ac370a055d"},{"url":"https://git.kernel.org/stable/c/07976405a3c71253e50533ee7b7a8b0dc16ab6ba"},{"url":"https://git.kernel.org/stable/c/86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc"}],"tags":["cve.org"],"ingestedAt":"2026-10-26T15:29:30.506Z","slug":"CVE-2026-99091","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix status of pending commands flushed on power off\n\ncmd_complete_rsp() receives a struct cmd_lookup and, for a pending\ncommand that has no cmd_complete callback, falls through to\ncmd_status_rsp(cmd, data). cmd_status_rsp() reads data as a u8 *, so\nthe status sent comes from the first byte of match->sk's\nrepresentation, not from match->mgmt_status.\n\ncommit f53e1c9c726d (\"Bluetooth: MGMT: Fix possible crash on\nmgmt_index_removed\") changed the callers' data from &status to &match\nand updated the cmd_complete branch to match->mgmt_status, but left\nthe fall-through passing data unchanged.\n\nIn mgmt_index_removed() match->sk is NULL, so every such command is\nanswered with status 0x00 (Success) instead of\nMGMT_STATUS_INVALID_INDEX. In __mgmt_power_off() it is NULL too,\nunless a Set Powered command was pending: then settings_rsp() has\nstored that command's socket in match->sk, and the byte sent comes\nfrom the socket pointer. Either way the status the caller set,\nMGMT_STATUS_NOT_POWERED (or MGMT_STATUS_INVALID_INDEX when the device\nis being unregistered), is lost.\n\nPass the status the callers set.\n\nThis was seen on a QCA9377 laptop: bluetoothd's Start Discovery,\npending when the adapter was powered off, was answered with Command\nStatus 0x00 and no parameters, and bluetoothd 5.72 crashed on the\nzero-length success. BlueZ master has since added the length check\non that path (\"adapter: Fix crash on short start discovery reply\",\nBlueZ a734b06059cb), but userspace should still be told Not Powered,\nnot Success.\n\nTested on Ubuntu 7.0.0-31 with a virtual controller (hci_vhci):\npower off is held in HCI Write Scan Enable while a Start Discovery is\nsubmitted, and the flush answers it with status 0x00 before this\nchange and 0x0f (Not Powered) after.\n\n## Affected\n\n- `Linux >= 4883296505aa7e4863c6869b689afb6005633b23 < 44ce36c5789ac84e65de1e98c32db9a5ac04ed47`\n- `Linux >= f53e1c9c726d83092167f2226f32bd3b73f26c21 < 7ed7e038b520cf0dfa12d61c2caddb95e2f6922d`\n- `Linux >= f53e1c9c726d83092167f2226f32bd3b73f26c21 < ec227cddd13cd7ac9077d263a73473ac370a055d`\n- `Linux >= f53e1c9c726d83092167f2226f32bd3b73f26c21 < 07976405a3c71253e50533ee7b7a8b0dc16ab6ba`\n- `Linux >= f53e1c9c726d83092167f2226f32bd3b73f26c21 < 86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc`\n- `Linux 19b40ca62607cef78369549d1af091f2fd558931`\n- `Linux 0cc47233af35fb5f10b5e6a027cb4ccd480caf9a`\n- `Linux 8c3f7943a29145d8a2d8e24893762f7673323eae`\n- `Linux >= 6.6.55 < 6.6.160`\n- `Linux >= 6.1.120 < 6.2`\n- `Linux >= 6.10.14 < 6.11`\n- `Linux >= 6.11.3 < 6.12`\n- `Linux 6.12`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}