CVE-2026-98632Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < f84e52829021d00bca8e067302f597c71af1f71a
- affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 718a8ffa180d469f99ad4f746f00cafd39456415
- affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 084be90948632a5a358821e687b11a14445aae76
- affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 2189a219397d8e73808a67c4aade837b635705da
- affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 03ced4687fb79286be7fdee0fc58d2c74de3e7bb
- affected b338d91703fae6f6afd67f3f75caa3b8f36ddef3 – < 71af682ba4692c2ed9ace4c3d4ca462ae368c029
- affected 6.1
- unaffected < 6.1
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.55 – ≤ 6.18.*
- unaffected 7.2.9 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/f84e52829021d00bca8e067302f597c71af1f71a (opens in a new tab)
- https://git.kernel.org/stable/c/718a8ffa180d469f99ad4f746f00cafd39456415 (opens in a new tab)
- https://git.kernel.org/stable/c/084be90948632a5a358821e687b11a14445aae76 (opens in a new tab)
- https://git.kernel.org/stable/c/2189a219397d8e73808a67c4aade837b635705da (opens in a new tab)
- https://git.kernel.org/stable/c/03ced4687fb79286be7fdee0fc58d2c74de3e7bb (opens in a new tab)
- https://git.kernel.org/stable/c/71af682ba4692c2ed9ace4c3d4ca462ae368c029 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103546 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98632)Record last updated .