Linux: Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel
What fixes it
- 718a8ffa180d469f99ad4f746f00cafd39456415LinuxCVE List
- 084be90948632a5a358821e687b11a14445aae76LinuxCVE List
- 2189a219397d8e73808a67c4aade837b635705daLinuxCVE List
- 03ced4687fb79286be7fdee0fc58d2c74de3e7bbLinuxCVE List
- 71af682ba4692c2ed9ace4c3d4ca462ae368c029LinuxCVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
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.
Text from CVE List
Affected versions 14
- Linuxaffected: b338d91703fae6f6afd67f3f75caa3b8f36ddef3 before f84e52829021d00bca8e067302f597c71af1f71aCVE List
- Linuxaffected: b338d91703fae6f6afd67f3f75caa3b8f36ddef3 before 718a8ffa180d469f99ad4f746f00cafd39456415CVE List
- Linuxaffected: b338d91703fae6f6afd67f3f75caa3b8f36ddef3 before 084be90948632a5a358821e687b11a14445aae76CVE List
- Linuxaffected: b338d91703fae6f6afd67f3f75caa3b8f36ddef3 before 2189a219397d8e73808a67c4aade837b635705daCVE List
- Linuxaffected: b338d91703fae6f6afd67f3f75caa3b8f36ddef3 before 03ced4687fb79286be7fdee0fc58d2c74de3e7bbCVE List
- Linuxaffected: b338d91703fae6f6afd67f3f75caa3b8f36ddef3 before 71af682ba4692c2ed9ace4c3d4ca462ae368c029CVE List
- Linuxaffected: 6.1CVE List
- Linuxunaffected: all versions before 6.1CVE List
- Linuxunaffected: 6.1.189 through 6.1.*CVE List
- Linuxunaffected: 6.6.158 through 6.6.*CVE List
- Linuxunaffected: 6.12.112 through 6.12.*CVE List
- Linuxunaffected: 6.18.55 through 6.18.*CVE List
- Linuxunaffected: 7.2.9 through 7.2.*CVE List
- Linuxunaffected: 7.3CVE List
References 6
- git.kernel.org/stable/c/f84e52829021d00bca8e067302f597c71af1f71aReferencevia CVE List
- git.kernel.org/stable/c/718a8ffa180d469f99ad4f746f00cafd39456415Referencevia CVE List
- git.kernel.org/stable/c/084be90948632a5a358821e687b11a14445aae76Referencevia CVE List
- git.kernel.org/stable/c/2189a219397d8e73808a67c4aade837b635705daReferencevia CVE List
- git.kernel.org/stable/c/03ced4687fb79286be7fdee0fc58d2c74de3e7bbReferencevia CVE List
- git.kernel.org/stable/c/71af682ba4692c2ed9ace4c3d4ca462ae368c029Referencevia CVE List