Bluetooth: MGMT: Fix status of pending commands flushed on power off

MITRE NVD CVE.ORG JSON API

Summary

CVECVE-2026-99091
StatePUBLISHED
AssignerLinux
Source PriorityCVE Program / NVD first with legacy fallback
Published2026-10-26 15:16:47 UTC
Updated2026-10-26 15:16:47 UTC
DescriptionIn 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.

Vendor Declared Affected Products

SourceVendorProductVersionPlatforms
CNA Linux Linux affected 4883296505aa7e4863c6869b689afb6005633b23 44ce36c5789ac84e65de1e98c32db9a5ac04ed47 git Not specified
CNA Linux Linux affected f53e1c9c726d83092167f2226f32bd3b73f26c21 7ed7e038b520cf0dfa12d61c2caddb95e2f6922d git Not specified
CNA Linux Linux affected f53e1c9c726d83092167f2226f32bd3b73f26c21 ec227cddd13cd7ac9077d263a73473ac370a055d git Not specified
CNA Linux Linux affected f53e1c9c726d83092167f2226f32bd3b73f26c21 07976405a3c71253e50533ee7b7a8b0dc16ab6ba git Not specified
CNA Linux Linux affected f53e1c9c726d83092167f2226f32bd3b73f26c21 86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc git Not specified
CNA Linux Linux affected 19b40ca62607cef78369549d1af091f2fd558931 git Not specified
CNA Linux Linux affected 0cc47233af35fb5f10b5e6a027cb4ccd480caf9a git Not specified
CNA Linux Linux affected 8c3f7943a29145d8a2d8e24893762f7673323eae git Not specified
CNA Linux Linux affected 6.6.55 6.6.160 semver Not specified
CNA Linux Linux affected 6.1.120 6.2 semver Not specified
CNA Linux Linux affected 6.10.14 6.11 semver Not specified
CNA Linux Linux affected 6.11.3 6.12 semver Not specified
CNA Linux Linux affected 6.12 Not specified
CNA Linux Linux unaffected 6.12 semver Not specified
CNA Linux Linux unaffected 6.6.160 6.6.* semver Not specified
CNA Linux Linux unaffected 6.12.113 6.12.* semver Not specified
CNA Linux Linux unaffected 6.18.57 6.18.* semver Not specified
CNA Linux Linux unaffected 7.2.11 7.2.* semver Not specified
CNA Linux Linux unaffected 7.3 * original_commit_for_fix Not specified

References

ReferenceSourceLinkTags
git.kernel.org/stable/c/07976405a3c71253e50533ee7b7a8b0dc16ab6ba 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/7ed7e038b520cf0dfa12d61c2caddb95e2f6922d 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/ec227cddd13cd7ac9077d263a73473ac370a055d 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/44ce36c5789ac84e65de1e98c32db9a5ac04ed47 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
git.kernel.org/stable/c/86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc 416baaa9-dc9f-4396-8d5f-8c081fb06d67 git.kernel.org
CVE Program record CVE.ORG www.cve.org canonical
NVD vulnerability detail NVD nvd.nist.gov canonical, analysis

© CVE.report 2026

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report