Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 07976405a3c71253e50533ee7b7a8b0dc16ab6ba, 44ce36c5789ac84e65de1e98c32db9a5ac04ed47, 6.1.191.

Low priority for now. Upgrade to Linux Linux 07976405a3c71253e50533ee7b7a8b0dc16ab6ba, 44ce36c5789ac84e65de1e98c32db9a5ac04ed47, 6.1.191 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 26, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-99091

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 0cc47233af35fb5f10b5e6a027cb4ccd480caf9a, 8c3f7943a29145d8a2d8e24893762f7673323eae, 6.12affected
    • 19b40ca62607cef78369549d1af091f2fd558931 and later · before bbc485ee811a74fc1d4733d0a2b0eb5aeb271a08affected · git
    • 4883296505aa7e4863c6869b689afb6005633b23 and later · before 44ce36c5789ac84e65de1e98c32db9a5ac04ed47affected · git
    • f53e1c9c726d83092167f2226f32bd3b73f26c21 and later · before 7ed7e038b520cf0dfa12d61c2caddb95e2f6922daffected · git
    • f53e1c9c726d83092167f2226f32bd3b73f26c21 and later · before ec227cddd13cd7ac9077d263a73473ac370a055daffected · git
    • f53e1c9c726d83092167f2226f32bd3b73f26c21 and later · before 07976405a3c71253e50533ee7b7a8b0dc16ab6baaffected · git
    • f53e1c9c726d83092167f2226f32bd3b73f26c21 and later · before 86ef0f58bdecdedb3a1240971c56d71b7e4ce3fcaffected · git
    • 6.1.120 and later · before 6.1.191affected · semver
    • 6.6.55 and later · before 6.6.160affected · semver
    • 6.10.14 and later · before 6.11affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.11-17.2.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-99089Oct 26, 2026 · ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM
    0Monitor
  • ← EarlierCVE-2026-99090Oct 26, 2026 · drm/amdgpu: serialize vblank counter reads against GPU reset
    0Monitor
  • Later →CVE-2026-99092Oct 26, 2026 · riscv: patch: fix handling of bpf-jit execmem addresses
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux07976405a3c71253e50533ee7b7a8b0dc16ab6baVendor (CNA)
Linux Linux44ce36c5789ac84e65de1e98c32db9a5ac04ed47Vendor (CNA)
Linux Linux6.1.191Vendor (CNA)
Linux Linux6.11Vendor (CNA)
Linux Linux6.12Vendor (CNA)
Linux Linux6.6.160Vendor (CNA)
Linux Linux7ed7e038b520cf0dfa12d61c2caddb95e2f6922dVendor (CNA)
Linux Linux86ef0f58bdecdedb3a1240971c56d71b7e4ce3fcVendor (CNA)
Linux Linuxbbc485ee811a74fc1d4733d0a2b0eb5aeb271a08Vendor (CNA)
Linux Linuxec227cddd13cd7ac9077d263a73473ac370a055dVendor (CNA)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 7, 2026+12 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records