Bluetooth: mgmt: Dequeue pending mesh_send_sync entries on cancel
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b338d91703fae6f6afd67f3f75caa3b8f36ddef3 · fixed in f84e52829021d00bca8e067302f597c71af1f71a; From b338d91703fae6f6afd67f3f75caa3b8f36ddef3 · fixed in 718a8ffa180d469f99ad4f746f00cafd39456415; From b338d91703fae6f6afd67f3f75caa3b8f36ddef3 · fixed in 084be90948632a5a358821e687b11a14445aae76; From b338d91703fae6f6afd67f3f75caa3b8f36ddef3 · fixed in 2189a219397d8e73808a67c4aade837b635705da; From b338d91703fae6f6afd67f3f75caa3b8f36ddef3 · fixed in 03ced4687fb79286be7fdee0fc58d2c74de3e7bb; From b338d91703fae6f6afd67f3f75caa3b8f36ddef3 · fixed in 71af682ba4692c2ed9ace4c3d4ca462ae368c029
- Linux Linux
6.1
- KernelLinux
From 6.1.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9