Vulnerability · Published Oct 26, 2026 · Assigned by Linux

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

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 93.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

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

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-99091
Debian:13linux6.12.113-1DEBIAN-CVE-2026-99091
Debian:14linux7.2.11-1DEBIAN-CVE-2026-99091
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.10linux7.3.0-10.10UBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.10linux-aws7.3.0-1004.4UBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.10linux-azureno fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.10linux-gcp7.3.0-1004.4UBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.10linux-oracle7.3.0-1004.4UBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.10linux-raspi7.3.0-1004.4UBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.10linux-realtime7.3.0-10.10.1UBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-99091
Ubuntu:26.10linux-riscv7.3.0-10.10.1UBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-99091
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-99091
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-99091

Affected products (as reported)

VendorProductVersions
Linux Linux 19b40ca62607cef78369549d1af091f2fd558931 – before bbc485ee811a74fc1d4733d0a2b0eb5aeb271a084883296505aa7e4863c6869b689afb6005633b23 – before 44ce36c5789ac84e65de1e98c32db9a5ac04ed47f53e1c9c726d83092167f2226f32bd3b73f26c21 – before 7ed7e038b520cf0dfa12d61c2caddb95e2f6922df53e1c9c726d83092167f2226f32bd3b73f26c21 – before ec227cddd13cd7ac9077d263a73473ac370a055df53e1c9c726d83092167f2226f32bd3b73f26c21 – before 07976405a3c71253e50533ee7b7a8b0dc16ab6baf53e1c9c726d83092167f2226f32bd3b73f26c21 – before 86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc0cc47233af35fb5f10b5e6a027cb4ccd480caf9a8c3f7943a29145d8a2d8e24893762f7673323eae
Linux Linux 6.12

References