Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f84e52829021d00bca8e067302f597c71af1f71a, Kernel 03ced4687fb79286be7fdee0fc58d2c74de3e7bb, Kernel 084be90948632a5a358821e687b11a14445aae76 and 8 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <f84e52829021d00bca8e067302f597c71af1f71a, >=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <03ced4687fb79286be7fdee0fc58d2c74de3e7bb, >=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <084be90948632a5a358821e687b11a14445aae76, >=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <2189a219397d8e73808a67c4aade837b635705da, >=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <718a8ffa180d469f99ad4f746f00cafd39456415, >=b338d91703fae6f6afd67f3f75caa3b8f36ddef3 <71af682ba4692c2ed9ace4c3d4ca462ae368c029, =6.1 | f84e52829021d00bca8e067302f597c71af1f71a, 03ced4687fb79286be7fdee0fc58d2c74de3e7bb, 084be90948632a5a358821e687b11a14445aae76, 2189a219397d8e73808a67c4aade837b635705da, 718a8ffa180d469f99ad4f746f00cafd39456415, 71af682ba4692c2ed9ace4c3d4ca462ae368c029 |
| linux-kernel: Kernel | >=6.13.0 <6.18.55, >=6.19.0 <7.2.9, >=6.2.0 <6.6.158, >=6.7.0 <6.12.112, >=6.1.0 <6.1.189 | 6.18.55, 7.2.9, 6.6.158, 6.12.112, 6.1.189 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket