CVE-2026-99091Bluetooth: MGMT: Fix status of pending commands flushed on power off

Description

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.

Timeline

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)

0.17% · top 94% of all CVEs (13 Nov 2026)

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

• Linux · Linux

  • affected 19b40ca62607cef78369549d1af091f2fd558931 – < bbc485ee811a74fc1d4733d0a2b0eb5aeb271a08
  • affected 4883296505aa7e4863c6869b689afb6005633b23 – < 44ce36c5789ac84e65de1e98c32db9a5ac04ed47
  • affected f53e1c9c726d83092167f2226f32bd3b73f26c21 – < 7ed7e038b520cf0dfa12d61c2caddb95e2f6922d
  • affected f53e1c9c726d83092167f2226f32bd3b73f26c21 – < ec227cddd13cd7ac9077d263a73473ac370a055d
  • affected f53e1c9c726d83092167f2226f32bd3b73f26c21 – < 07976405a3c71253e50533ee7b7a8b0dc16ab6ba
  • affected f53e1c9c726d83092167f2226f32bd3b73f26c21 – < 86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc
  • affected 0cc47233af35fb5f10b5e6a027cb4ccd480caf9a
  • affected 8c3f7943a29145d8a2d8e24893762f7673323eae
  • affected 6.1.120 – < 6.1.191
  • affected 6.6.55 – < 6.6.160
  • affected 6.10.14 – < 6.11
  • affected 6.11.3 – < 6.12

• Linux · Linux

  • affected 6.12
  • unaffected < 6.12
  • unaffected 6.1.191 – ≤ 6.1.*
  • unaffected 6.6.160 – ≤ 6.6.*
  • unaffected 6.12.113 – ≤ 6.12.*
  • unaffected 6.18.57 – ≤ 6.18.*
  • unaffected 7.2.11 – ≤ 7.2.*
  • unaffected 7.3 – ≤ *

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2026-109897 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-99091](https://cveledger.app/badge/CVE-2026-99091.svg)](https://cveledger.app/cve/CVE-2026-99091)

Record last updated 30 Oct 2026, 12:41 UTC.