# CVE-2026-98632: Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel

> A use-after-free in the Linux kernel Bluetooth mesh subsystem allows attackers to cause denial of service or execute arbitrary code via crafted Bluetooth transmissions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108921, BELL-CVE-2026-98632, DEBIAN-CVE-2026-98632, GHSA-qvq7-5mpj-hvwr, UBUNTU-CVE-2026-98632

## What is CVE-2026-98632?

CVE-2026-98632 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel

In send_cancel(), pending mesh_tx objects are removed from the
hdev->mesh_pending list and freed via mesh_send_complete().  However, if
a mesh transmission was already queued onto hdev->cmd_sync_work_list via
mesh_next(), the queued entry retains a raw pointer to mesh_tx.

When hci_cmd_sync_work later processes the entry, it attempts to execute
mesh_send_sync and its destroy callback mesh_send_start_complete using
the already freed mesh_tx pointer, leading to a use-after-free.

Fix this by invoking hci_cmd_sync_dequeue() for mesh_send_sync on the
target mesh_tx before completing it.  If the entry is found and dequeued,
its destroy callback will complete and free the object; otherwise,
mesh_send_complete() is called directly.

Additionally, ensure the transmission queue advances after cancellation
or errors.  In mesh_send_start_complete(), call mesh_next() on error
unless err is -ECANCELED, because hci_cmd_sync_dequeue() holds
hdev->cmd_sync_work_lock and calling mesh_next() synchronously would
deadlock.  Instead, advance the queue in send_cancel() once the lock is
released and if no transmission is in progress.

## Which versions are affected by CVE-2026-98632?


## How do I fix CVE-2026-98632?

Apply the vendor's patch.

## Is CVE-2026-98632 being exploited?

There is no known exploitation of CVE-2026-98632 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98632 and fix it if it is affected.

What it is: CVE-2026-98632 is an use after free vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98632 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98632/ (Markdown: https://insights.sbomify.com/CVE-2026-98632/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98632
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98632
- OSV: https://osv.dev/vulnerability/CVE-2026-98632

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98632/
Summaries are generated and may contain mistakes; the official description above is the record.