{
  "cveId": "CVE-2026-99091",
  "url": "https://patchblox.com/security/cve/CVE-2026-99091",
  "summary": "CVE-2026-99091 is fixed in linux on 1 platform, first by DEBIAN-CVE-2026-99091, released October 27, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: MGMT: Fix status of pending commands...",
  "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-\u003Esk\u0027s representation, not from match-\u003Emgmt_status.  commit f53e1c9c726d (\u0022Bluetooth: MGMT: Fix possible crash on mgmt_index_removed\u0022) changed the callers\u0027 data from \u0026status to \u0026match and updated the cmd_complete branch to match-\u003Emgmt_status, but left the fall-through passing data unchanged.  In mgmt_index_removed() match-\u003Esk 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\u0027s socket in match-\u003Esk, 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\u0027s 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 (\u0022adapter: Fix crash on short start discovery reply\u0022, 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.",
  "published": "2026-10-26T15:16:47Z",
  "severity": "",
  "epss": 0.00168,
  "epssPercentile": 0.06234,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.113-1",
      "fix": "DEBIAN-CVE-2026-99091",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-99091",
      "released": "2026-10-27T21:14:52Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.2.11-1",
      "fix": "DEBIAN-CVE-2026-99091",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-99091",
      "released": "2026-10-27T21:14:52Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T07:25:28Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}