Bluetooth: MGMT: Fix possible deadlock in mgmt_remove_adv_monitor_complete
Subsystems (2)
Luiz Augusto von Dentz
maintainerPATCH 1/3 Bluetooth: MGMT: Fix possible deadlock in mgmt_remove_adv_monitor_complete
From: Luiz Augusto von Dentz <[email protected]>
This fixes the following deadlock:
--------------------------------------------
syz.4.423/7568 is trying to acquire lock:ffff888068c48078 (&hdev->lock){+.+.}-{4:4}, at: mgmt_remove_adv_monitor_complete+0x9e/0x2e0 net/bluetooth/mgmt.c:5524
but task is already holding lock:ffff888068c48078 (&hdev->lock){+.+.}-{4:4}, at: hci_dev_close_sync+0x3ab/0x11a0 net/bluetooth/hci_sync.c:5200
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
---- lock(&hdev->lock);
lock(&hdev->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
3 locks held by syz.4.423/7568:
#0: ffff888068c48d80 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_do_close+0x26/0x90 net/bluetooth/hci_core.c:480 #1: ffff888068c48078 (&hdev->lock){+.+.}-{4:4}, at: hci_dev_close_sync+0x3ab/0x11a0 net/bluetooth/hci_sync.c:5200 #2: ffff888068c48690 (&hdev->cmd_sync_work_lock){+.+.}-{4:4}, at: hci_cmd_sync_dequeue+0x50/0x1f0 net/bluetooth/hci_sync.c:887
--- net/bluetooth/mgmt.c | 8 ++++++++ 1 file changed, 8 insertions(+)
net/bluetooth/mgmt.c +8 -0
@@ -5189,6 +5189,14 @@ static void mgmt_add_adv_patterns_monitor_complete(struct hci_dev *hdev,struct mgmt_pending_cmd *cmd = data;struct adv_monitor *monitor = cmd->user_data; +/* This is likely the result of hdev being closed and mgmt_index_removed +* is attempting to clean up any pending command so +* hci_adv_monitors_clear is about to be called which will take care of +* freeing the adv_monitor instances. +*/ +if (status == -ECANCELED ) +return ; +hci_dev_lock (hdev); rp.monitor_handle =cpu_to_le16 (monitor->handle);
Signature · 1 line
2.50.1
Luiz Augusto von Dentz
maintainerPATCH 2/3 Bluetooth: hci_event: Fix UAF in hci_conn_tx_dequeue
From: Luiz Augusto von Dentz <[email protected]>
This fixes the following UAF caused by not properly locking hdev when processing HCI_EV_NUM_COMP_PKTS:
BUG: KASAN: slab-use-after-free in hci_conn_tx_dequeue+0x1be/0x220 net/bluetooth/hci_conn.c:3036 Read of size 4 at addr ffff8880740f0940 by task kworker/u11:0/54 CPU: 1 UID: 0 PID: 54 Comm: kworker/u11:0 Not tainted 6.16.0-rc7 #3 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 Workqueue: hci1 hci_rx_work Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x230 mm/kasan/report.c:480 kasan_report+0x118/0x150 mm/kasan/report.c:593 hci_conn_tx_dequeue+0x1be/0x220 net/bluetooth/hci_conn.c:3036 hci_num_comp_pkts_evt+0x1c8/0xa50 net/bluetooth/hci_event.c:4404 hci_event_func net/bluetooth/hci_event.c:7477 [inline] hci_event_packet+0x7e0/0x1200 net/bluetooth/hci_event.c:7531 hci_rx_work+0x46a/0xe80 net/bluetooth/hci_core.c:4070 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16-rc7/arch/x86/entry/entry_64.S:245 </TASK> Allocated by task 54: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __kmalloc_cache_noprof+0x230/0x3d0 mm/slub.c:4359 kmalloc_noprof include/linux/slab.h:905 [inline] kzalloc_noprof include/linux/slab.h:1039 [inline] __hci_conn_add+0x233/0x1b30 net/bluetooth/hci_conn.c:939 le_conn_complete_evt+0x3d6/0x1220 net/bluetooth/hci_event.c:5628 hci_le_enh_conn_complete_evt+0x189/0x470 net/bluetooth/hci_event.c:5794 hci_event_func net/bluetooth/hci_event.c:7474 [inline] hci_event_packet+0x78c/0x1200 net/bluetooth/hci_event.c:7531 hci_rx_work+0x46a/0xe80 net/bluetooth/hci_core.c:4070 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16-rc7/arch/x86/entry/entry_64.S:245 Freed by task 9572: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:576 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x62/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2381 [inline] slab_free mm/slub.c:4643 [inline] kfree+0x18e/0x440 mm/slub.c:4842 device_release+0x9c/0x1c0 kobject_cleanup lib/kobject.c:689 [inline] kobject_release lib/kobject.c:720 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x22b/0x480 lib/kobject.c:737 hci_conn_cleanup net/bluetooth/hci_conn.c:175 [inline] hci_conn_del+0x8ff/0xcb0 net/bluetooth/hci_conn.c:1173 hci_abort_conn_sync+0x5d1/0xdf0 net/bluetooth/hci_sync.c:5689 hci_cmd_sync_work+0x210/0x3a0 net/bluetooth/hci_sync.c:332 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16-rc7/arch/x86/entry/entry_64.S:245
--- net/bluetooth/hci_event.c | 4 ++++ 1 file changed, 4 insertions(+)
net/bluetooth/hci_event.c +4 -0
@@ -4391,6 +4391,8 @@ static void hci_num_comp_pkts_evt(struct hci_dev *hdev, void *data,bt_dev_dbg (hdev,"num %d" , ev->num); +hci_dev_lock (hdev); +for (i =0 ; i < ev->num; i++) {struct hci_comp_pkts_info *info = &ev->handles[i];struct hci_conn *conn;
@@ -4462,6 +4464,8 @@ static void hci_num_comp_pkts_evt(struct hci_dev *hdev, void *data, }queue_work (hdev->workqueue, &hdev->tx_work); + +hci_dev_unlock (hdev); } static void hci_mode_change_evt(struct hci_dev *hdev, void *data,
Signature · 1 line
2.50.1
Luiz Augusto von Dentz
maintainerPATCH 3/3 Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync
In reply to Luiz Augusto von DentzFrom: Luiz Augusto von Dentz <[email protected]>
This fixes the following UFA in hci_acl_create_conn_sync where a connection still pending is command submission (conn->state == BT_OPEN) maybe freed, also since this also can happen with the likes of hci_le_create_conn_sync fix it as well:
BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5ef/0x790 net/bluetooth/hci_sync.c:6861 Write of size 2 at addr ffff88805ffcc038 by task kworker/u11:2/9541 CPU: 1 UID: 0 PID: 9541 Comm: kworker/u11:2 Not tainted 6.16.0-rc7 #3 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 Workqueue: hci3 hci_cmd_sync_work Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x230 mm/kasan/report.c:480 kasan_report+0x118/0x150 mm/kasan/report.c:593 hci_acl_create_conn_sync+0x5ef/0x790 net/bluetooth/hci_sync.c:6861 hci_cmd_sync_work+0x210/0x3a0 net/bluetooth/hci_sync.c:332 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16-rc7/arch/x86/entry/entry_64.S:245 </TASK> Allocated by task 123736: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __kmalloc_cache_noprof+0x230/0x3d0 mm/slub.c:4359 kmalloc_noprof include/linux/slab.h:905 [inline] kzalloc_noprof include/linux/slab.h:1039 [inline] __hci_conn_add+0x233/0x1b30 net/bluetooth/hci_conn.c:939 hci_conn_add_unset net/bluetooth/hci_conn.c:1051 [inline] hci_connect_acl+0x16c/0x4e0 net/bluetooth/hci_conn.c:1634 pair_device+0x418/0xa70 net/bluetooth/mgmt.c:3556 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:712 [inline] __sock_sendmsg+0x219/0x270 net/socket.c:727 sock_write_iter+0x258/0x330 net/socket.c:1131 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x54b/0xa90 fs/read_write.c:686 ksys_write+0x145/0x250 fs/read_write.c:738 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 103680: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:576 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x62/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:233 [inline] slab_free_hook mm/slub.c:2381 [inline] slab_free mm/slub.c:4643 [inline] kfree+0x18e/0x440 mm/slub.c:4842 device_release+0x9c/0x1c0 kobject_cleanup lib/kobject.c:689 [inline] kobject_release lib/kobject.c:720 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x22b/0x480 lib/kobject.c:737 hci_conn_cleanup net/bluetooth/hci_conn.c:175 [inline] hci_conn_del+0x8ff/0xcb0 net/bluetooth/hci_conn.c:1173 hci_conn_complete_evt+0x3c7/0x1040 net/bluetooth/hci_event.c:3199 hci_event_func net/bluetooth/hci_event.c:7477 [inline] hci_event_packet+0x7e0/0x1200 net/bluetooth/hci_event.c:7531 hci_rx_work+0x46a/0xe80 net/bluetooth/hci_core.c:4070 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16-rc7/arch/x86/entry/entry_64.S:245 Last potentially related work creation: kasan_save_stack+0x3e/0x60 mm/kasan/common.c:47 kasan_record_aux_stack+0xbd/0xd0 mm/kasan/generic.c:548 insert_work+0x3d/0x330 kernel/workqueue.c:2183 __queue_work+0xbd9/0xfe0 kernel/workqueue.c:2345 queue_delayed_work_on+0x18b/0x280 kernel/workqueue.c:2561 pairing_complete+0x1e7/0x2b0 net/bluetooth/mgmt.c:3451 pairing_complete_cb+0x1ac/0x230 net/bluetooth/mgmt.c:3487 hci_connect_cfm include/net/bluetooth/hci_core.h:2064 [inline] hci_conn_failed+0x24d/0x310 net/bluetooth/hci_conn.c:1275 hci_conn_complete_evt+0x3c7/0x1040 net/bluetooth/hci_event.c:3199 hci_event_func net/bluetooth/hci_event.c:7477 [inline] hci_event_packet+0x7e0/0x1200 net/bluetooth/hci_event.c:7531 hci_rx_work+0x46a/0xe80 net/bluetooth/hci_core.c:4070 process_one_work kernel/workqueue.c:3238 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 home/kwqcheii/source/fuzzing/kernel/kasan/linux-6.16-rc7/arch/x86/entry/entry_64.S:245
--- include/net/bluetooth/hci_core.h | 21 +++++++++++++++++++++ net/bluetooth/hci_event.c | 26 +++++++++++++++++++++++--- 2 files changed, 44 insertions(+), 3 deletions(-)
include/net/bluetooth/hci_core.h +21 -0
@@ -1246,6 +1246,27 @@ static inline struct hci_conn *hci_conn_hash_lookup_ba(struct hci_dev *hdev,return NULL ; } +static inline struct hci_conn *hci_conn_hash_lookup_role (struct hci_dev *hdev, +__u8 type,__u8 role, +bdaddr_t *ba) +{ +struct hci_conn_hash *h = &hdev->conn_hash; +struct hci_conn *c; + +rcu_read_lock (); + +list_for_each_entry_rcu (c, &h->list, list) { +if (c->type == type && c->role == role && !bacmp (&c->dst, ba)) { +rcu_read_unlock (); +return c; + } + } + +rcu_read_unlock (); + +return NULL ; +} +static inline struct hci_conn *hci_conn_hash_lookup_le (struct hci_dev *hdev,bdaddr_t *ba,__u8 ba_type)
net/bluetooth/hci_event.c +23 -3
@@ -3087,8 +3087,18 @@ static void hci_conn_complete_evt(struct hci_dev *hdev, void *data,hci_dev_lock (hdev); +/* Check for existing connection: +* +* 1. If it doesn't exist then it must be receiver/slave role. +* 2. If it does exist confirm that it is connecting/BT_CONNECT in case +* of initiator/master role since there could be a collision where +* either side is attempting to connect or something like a fuzzing +* testing is trying to play tricks to destroy the hcon object before +* it even attempts to connect (e.g. hcon->state == BT_OPEN). +*/ conn =hci_conn_hash_lookup_ba (hdev, ev->link_type, &ev->bdaddr); -if (!conn) { +if (!conn || + (conn->role ==HCI_ROLE_MASTER && conn->state !=BT_CONNECT )) {/* In case of error status and there is no connection pending * just unlock as there is nothing to cleanup. */
@@ -5628,8 +5638,18 @@ static void le_conn_complete_evt(struct hci_dev *hdev, u8 status,*/ hci_dev_clear_flag (hdev,HCI_LE_ADV ); - conn =hci_conn_hash_lookup_ba (hdev,LE_LINK , bdaddr); -if (!conn) { +/* Check for existing connection: +* +* 1. If it doesn't exist then use the role to create a new object. +* 2. If it does exist confirm that it is connecting/BT_CONNECT in case +* of initiator/master role since there could be a collision where +* either side is attempting to connect or something like a fuzzing +* testing is trying to play tricks to destroy the hcon object before +* it even attempts to connect (e.g. hcon->state == BT_OPEN). +*/ + conn =hci_conn_hash_lookup_role (hdev,LE_LINK , role, bdaddr); +if (!conn || + (conn->role ==HCI_ROLE_MASTER && conn->state !=BT_CONNECT )) {/* In case of error status and there is no connection pending * just unlock as there is nothing to cleanup. */
Signature · 1 line
2.50.1
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/project/bluetooth/list/?series=997029
---Test result---
Test Summary:
CheckPatch PENDING 0.55 seconds GitLint PENDING 0.40 seconds SubjectPrefix PASS 0.20 seconds BuildKernel PASS 23.91 seconds CheckAllWarning PASS 26.80 seconds CheckSparse WARNING 29.84 seconds BuildKernel32 PASS 24.02 seconds TestRunnerSetup PASS 475.32 seconds TestRunner_l2cap-tester PASS 24.60 seconds TestRunner_iso-tester PASS 38.68 seconds TestRunner_bnep-tester PASS 5.77 seconds TestRunner_mgmt-tester FAIL 129.14 seconds TestRunner_rfcomm-tester PASS 9.33 seconds TestRunner_sco-tester PASS 14.54 seconds TestRunner_ioctl-tester PASS 9.94 seconds TestRunner_mesh-tester FAIL 11.43 seconds TestRunner_smp-tester PASS 8.50 seconds TestRunner_userchan-tester PASS 6.18 seconds IncrementalBuild PENDING 0.45 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.105 seconds
##############################
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.125 seconds Mesh - Send cancel - 2 Timed out 1.998 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series Output:
---
Regards,
Linux Bluetooth
Dear Luiz,
Thank you for the patch.
Am 29.08.25 um 21:21 schrieb Luiz Augusto von Dentz:
Quoted 45 lines
From: Luiz Augusto von Dentz <[email protected]>
This fixes the following deadlock:
--------------------------------------------
syz.4.423/7568 is trying to acquire lock:ffff888068c48078(&hdev->lock){+.+.}-{4:4}, at:mgmt_remove_adv_monitor_complete+0x9e/0x2e0net/bluetooth/mgmt.c:5524but task is already holding lock:
ffff888068c48078(&hdev->lock){+.+.}-{4:4}, at:hci_dev_close_sync+0x3ab/0x11a0net/bluetooth/hci_sync.c:5200other info that might help us debug this:
Possible unsafe locking scenario:CPU0 ---- lock(&hdev->lock); lock(&hdev->lock);*** DEADLOCK ***
May be due to missing lock nesting notation
3 locks held by syz.4.423/7568:
#0:ffff888068c48d80(&hdev->req_lock){+.+.}-{4:4}, at:hci_dev_do_close+0x26/0x90net/bluetooth/hci_core.c:480#1:ffff888068c48078(&hdev->lock){+.+.}-{4:4}, at:hci_dev_close_sync+0x3ab/0x11a0net/bluetooth/hci_sync.c:5200#2:ffff888068c48690(&hdev->cmd_sync_work_lock){+.+.}-{4:4}, at:hci_cmd_sync_dequeue+0x50/0x1f0net/bluetooth/hci_sync.c:887Fixes Fixes: b747a83690c8 ("Bluetooth: hci_sync: Refactor add Adv Monitor")Reported-by [email protected]Signed-off-by Luiz Augusto von Dentz <[email protected]>--- net/bluetooth/mgmt.c | 8 ++++++++ 1 file changed, 8 insertions(+)net/bluetooth/mgmt.c +1
-0@@ -5189,6 +5189,14 @@ static void mgmt_add_adv_patterns_monitor_complete(struct hci_dev *hdev,struct mgmt_pending_cmd *cmd = data;struct adv_monitor *monitor = cmd->user_data; +/* This is likely the result of hdev being closed and mgmt_index_removed
net/bluetooth/mgmt.c static void mgmt_add_adv_patterns_monitor_complete(struct hci_dev *hdev, · line 5202
Quoted 10 lines
net/bluetooth/mgmt.c +7
-0+* is attempting to clean up any pending command so +* hci_adv_monitors_clear is about to be called which will take care of +* freeing the adv_monitor instances. +*/ +if (status == -ECANCELED ) +return ; +hci_dev_lock (hdev); rp.monitor_handle =cpu_to_le16 (monitor->handle);
Kind regards,
Paul
This series was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <[email protected]>:
Hello:
This series was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz <[email protected]>:
Quoted 9 lines · On Fri, 29 Aug 2025 15:21:02 -0400 you wrote:
From: Luiz Augusto von Dentz <[email protected]>
This fixes the following deadlock:
--------------------------------------------
syz.4.423/7568 is trying to acquire lock:ffff888068c48078(&hdev->lock){+.+.}-{4:4}, at:mgmt_remove_adv_monitor_complete+0x9e/0x2e0net/bluetooth/mgmt.c:5524[...]
Here is the summary with links:
- [v1,1/3] Bluetooth: MGMT: Fix possible deadlock in mgmt_remove_adv_monitor_complete (no matching commit)
- [v1,2/3] Bluetooth: hci_event: Fix UAF in hci_conn_tx_dequeue
https://git.kernel.org/bluetooth/bluetooth-next/c/6b74ce021062 - [v1,3/3] Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync https://git.kernel.org/bluetooth/bluetooth-next/c/b6018d6825ce
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html