VulnerabilityPublished 26 Oct 2026

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

Source GCVE Database

Authoritative record:CVE-2026-99091· Medium

Not known to be exploited · fixed in ec227cddd13cd7ac9077d263a73473ac370a055d : update Linux kernel when convenient.

Data as of 26 Oct 2026, 16:31 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in ec227cddd13cd7ac9077d263a73473ac370a055d, 07976405a3c71253e50533ee7b7a8b0dc16ab6ba, 86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc +6

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-75m9-vh6c-66mx

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=6.6.55 <6.6.160 >=6.1.120 <6.2 >=6.10.14 <6.11 >=6.11.3 <6.12	Fixed in ec227cddd13cd7ac9077d263a73473ac370a055d 07976405a3c71253e50533ee7b7a8b0dc16ab6ba 86ef0f58bdecdedb3a1240971c56d71b7e4ce3fc 44ce36c5789ac84e65de1e98c32db9a5ac04ed47 7ed7e038b520cf0dfa12d61c2caddb95e2f6922d 6.12 6.11 6.6.160 6.2
LinuxLinux	Affected =6.12	Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel to correctly pass the status set by callers for pending commands flushed on power off. Users should update to a kernel version that includes this fix. BlueZ has also added length checks to prevent crashes on short replies. No additional mitigation is required once the kernel is updated.

Description

A vulnerability in the Linux kernel Bluetooth management subsystem caused pending commands flushed on power off to report incorrect success status instead of the actual error status. This could lead to user-space components like bluetoothd misinterpreting the device state, potentially causing crashes.

Impact

User-space Bluetooth management daemons may receive incorrect success status for commands flushed during adapter power off, leading to misinterpretation of device state and potential crashes, as demonstrated by bluetoothd 5.72 crashing on a zero-length success response. This impacts reliability and stability of Bluetooth management on affected Linux kernels.

Summary

The Linux kernel Bluetooth MGMT interface had a flaw where cmd_complete_rsp() would fall through to cmd_status_rsp() passing incorrect data, causing the status of pending commands flushed on power off to be reported as 0x00 (Success) instead of the intended error status such as MGMT_STATUS_NOT_POWERED or MGMT_STATUS_INVALID_INDEX. This was due to passing a socket pointer instead of the correct status byte. The issue was observed on a QCA9377 laptop where bluetoothd crashed when receiving a zero-length success response to a Start Discovery command during power off. The fix involves passing the correct status set by the caller to avoid misleading success responses.

References

Community reviews

Loading reviews…