Bluetooth: hci_sync: Fix inquiry cache use-after-free
Subsystems (3)
PATCH 1/1 Bluetooth: hci_sync: Fix inquiry cache use-after-free
The sync command worker holds hdev->req_lock, but inquiry-cache updates and flushes use hdev->lock. Both hci_acl_create_conn_sync() and hci_stop_discovery_sync() look up entries and read their fields without taking hdev->lock.
After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire hdev->lock and flush the cache, freeing the entry. The worker then reads the freed entry while preparing a create-connection or remote-name-cancel command. The list traversal also races with cache updates and removal.
KASAN reported these accesses:
BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_acl_create_conn_sync+0x5f1/0x650 hci_cmd_sync_work+0x13c/0x290 Allocated by task 90: hci_inquiry_cache_update+0x3e6/0x7d0 hci_inquiry_result_evt+0x3cb/0x560 Freed by task 93: hci_inquiry_cache_flush+0x111/0x2b0 hci_inquiry+0x2f2/0x780 hci_sock_ioctl+0x269/0x5f0 BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_stop_discovery_sync+0x3b1/0x3c0 hci_cmd_sync_work+0x173/0x300 Allocated by task 86: hci_inquiry_cache_update+0x483/0x940 hci_inquiry_result_evt+0x3cb/0x560 Freed by task 91: hci_inquiry_cache_flush+0x13e/0x2f0 hci_inquiry+0x2f2/0x780 hci_sock_ioctl+0x269/0x5f0
Hold hdev->lock across each lookup and all reads from its result. Copy the remote address before unlocking so discovery cancellation does not retain a cache entry pointer. Release the lock before sending synchronous HCI commands, since their completion handlers may need the same lock.
--- net/bluetooth/hci_sync.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
net/bluetooth/hci_sync.c +11 -2
@@ -5764,6 +5764,7 @@ int hci_stop_discovery_sync(struct hci_dev *hdev) {struct discovery_state *d = &hdev->discovery;struct inquiry_entry *e; +bdaddr_t addr;int err;bt_dev_dbg (hdev,"state %u" , hdev->discovery.state);
@@ -5799,15 +5800,21 @@ int hci_stop_discovery_sync(struct hci_dev *hdev)return 0 ;if (d->state ==DISCOVERY_RESOLVING || d->state ==DISCOVERY_STOPPING ) { +hci_dev_lock (hdev); e =hci_inquiry_cache_lookup_resolve (hdev,BDADDR_ANY ,NAME_PENDING ); -if (!e) +if (!e) { +hci_dev_unlock (hdev);return 0 ; + } + +bacpy (&addr, &e->data.bdaddr); +hci_dev_unlock (hdev);/* Ignore cancel errors since it should interfere with stopping * of the discovery. */ -hci_remote_name_cancel_sync (hdev, &e->data.bdaddr); +hci_remote_name_cancel_sync (hdev, &addr); }return 0 ;
@@ -7236,6 +7243,7 @@ static int hci_acl_create_conn_sync(struct hci_dev *hdev, void *data)bacpy (&cp.bdaddr, &conn->dst); cp.pscan_rep_mode =0x02 ; +hci_dev_lock (hdev); ie =hci_inquiry_cache_lookup (hdev, &conn->dst);if (ie) {if (inquiry_entry_age (ie) <=INQUIRY_ENTRY_AGE_MAX ) {
@@ -7247,6 +7255,7 @@ static int hci_acl_create_conn_sync(struct hci_dev *hdev, void *data)memcpy (conn->dev_class, ie->data.dev_class,3 ); } +hci_dev_unlock (hdev); cp.pkt_type =cpu_to_le16 (conn->pkt_type);if (lmp_rswitch_capable (hdev) && !(hdev->link_mode &HCI_LM_MASTER ))
Signature · 1 line
2.43.0
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/series/1174571/
---Test result---
Test Summary:
CheckPatch PASS 0.63 seconds VerifyFixes PASS 0.08 seconds VerifySignedoff PASS 0.39 seconds GitLint PASS 0.24 seconds SubjectPrefix PASS 0.07 seconds BuildKernel PASS 30.31 seconds CheckAllWarning PASS 33.89 seconds CheckSparse PASS 36.41 seconds BuildKernel32 PASS 29.52 seconds CheckKernelLLVM PASS 36.09 seconds TestRunnerSetup PASS 833.38 seconds TestRunner_l2cap-tester PASS 16.59 seconds TestRunner_iso-tester PASS 41.01 seconds TestRunner_bnep-tester PASS 3.06 seconds TestRunner_mgmt-tester PASS 61.38 seconds TestRunner_rfcomm-tester PASS 4.43 seconds TestRunner_sco-tester PASS 7.60 seconds TestRunner_ioctl-tester PASS 4.61 seconds TestRunner_mesh-tester FAIL 7.77 seconds TestRunner_smp-tester PASS 4.29 seconds TestRunner_userchan-tester PASS 9.43 seconds TestRunner_6lowpan-tester PASS 4.57 seconds IncrementalBuild PASS 27.60 seconds
Details
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.408 seconds Mesh - Send cancel - 2 Timed out 1.999 seconds
https://github.com/bluez/bluetooth-next/pull/825
---
Regards,
Linux Bluetooth
This patch was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <[email protected]>:
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <[email protected]>:
Quoted 11 lines · On Sun, 27 Sep 2026 01:28:31 +0800 you wrote:
The sync command worker holds
hdev->req_lock, but inquiry-cache updates and flushes usehdev->lock. Bothhci_acl_create_conn_sync()andhci_stop_discovery_sync()look up entries and read their fields without takinghdev->lock.After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire
hdev->lockand flush the cache, freeing the entry. The worker then reads the freed entry while preparing a create-connection or remote-name-cancel command. The list traversal also races with cache updates and removal.[...]
Here is the summary with links:
- Bluetooth: hci_sync: Fix inquiry cache use-after-free
https://git.kernel.org/bluetooth/bluetooth-next/c/8ed67535fdff
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html