CVE-2026-99091: Linux

EPSS: 0.2% probability of exploitation activity in the next 30 days.

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

The record states a fixed version for each range of affected versions. Update to the one for the range your version is in: a later release on another branch may not have the fix.

  • Linux, from 6.1.120, before 6.1.191: fixed in 6.1.191
  • Linux, from 6.6.55, before 6.6.160: fixed in 6.6.160
  • Linux, from 6.10.14, before 6.11: fixed in 6.11
  • Linux, from 6.11.3, before 6.12: fixed in 6.12
  • Linux, from 6.12, before 6.12.113: fixed in 6.12.113
  • Linux, from 6.13, before 6.18.57: fixed in 6.18.57
  • Linux, from 6.19, before 7.2.11: fixed in 7.2.11

Affected products

  • Linux Linux: from 6.1.120, before 6.1.191 (fixed in 6.1.191); from 6.6.55, before 6.6.160 (fixed in 6.6.160); from 6.10.14, before 6.11 (fixed in 6.11); from 6.11.3, before 6.12 (fixed in 6.12); from 6.12, before 6.12.113 (fixed in 6.12.113); from 6.13, before 6.18.57 (fixed in 6.18.57); …

Published 2026-10-26. Last modified 2026-10-30.