Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.189, 6.12.112, 6.18.55, 6.6.158, 7.2.9
- CVEs
- CVE-2026-98632
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 13:23 UTC · Revision 1
Source evidence
Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel
core-osv · Original sourcePublished 18 Oct 2026, 15:19 UTC
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.
osv:CVE-2026-98632
Kernel
Fixed versions: 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9
Complete source record
{
"id": "2d1e557c5b809583a225a812023f096b55c61cf9466fb83b785e3d392ddc4ded",
"url": "https://osv.dev/vulnerability/CVE-2026-98632",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel",
"summary": "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.",
"evidence": "osv:CVE-2026-98632",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.189",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.158",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.112",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.55",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-98632",
"aliases": [
"CVE-2026-98632"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "b338d91703fae6f6afd67f3f75caa3b8f36ddef3"
},
{
"fixed": "f84e52829021d00bca8e067302f597c71af1f71a"
},
{
"fixed": "718a8ffa180d469f99ad4f746f00cafd39456415"
},
{
"fixed": "084be90948632a5a358821e687b11a14445aae76"
},
{
"fixed": "2189a219397d8e73808a67c4aade837b635705da"
},
{
"fixed": "03ced4687fb79286be7fdee0fc58d2c74de3e7bb"
},
{
"fixed": "71af682ba4692c2ed9ace4c3d4ca462ae368c029"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98632.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.1.0"
},
{
"fixed": "6.1.189"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.158"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.112"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.55"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98632.json"
}
}
],
"modified": "2026-10-28T02:30:28.900394108Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/03ced4687fb79286be7fdee0fc58d2c74de3e7bb",
"https://git.kernel.org/stable/c/084be90948632a5a358821e687b11a14445aae76",
"https://git.kernel.org/stable/c/2189a219397d8e73808a67c4aade837b635705da",
"https://git.kernel.org/stable/c/718a8ffa180d469f99ad4f746f00cafd39456415",
"https://git.kernel.org/stable/c/71af682ba4692c2ed9ace4c3d4ca462ae368c029",
"https://git.kernel.org/stable/c/f84e52829021d00bca8e067302f597c71af1f71a",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98632.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-98632",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98632.json"
}
},
"related_cves": [
{
"value": "CVE-2026-98632",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 495843,
"published_at": "2026-10-18T15:19:56.287+00:00"
}