* Re: [PATCH] Bluetooth: L2CAP: Fix use-after-free in l2cap_chan_timeout()
2026-03-19 15:14 [PATCH] Bluetooth: L2CAP: Fix use-after-free in l2cap_chan_timeout() Hyunwoo Kim
@ 2026-03-19 15:55 ` Luiz Augusto von Dentz
2026-03-19 16:36 ` bluez.test.bot
2026-04-09 20:01 ` bluez.test.bot
2 siblings, 0 replies; 4+ messages in thread
From: Luiz Augusto von Dentz @ 2026-03-19 15:55 UTC (permalink / raw)
To: Hyunwoo Kim; +Cc: marcel, johan.hedberg, linux-bluetooth
Hi Hyunwoo,
On Thu, Mar 19, 2026 at 11:14 AM Hyunwoo Kim <imv4bel@gmail.com> wrote:
>
> l2cap_chan_timeout() reads chan->conn without holding any lock and
> without taking a reference on the connection. If l2cap_conn_del()
> frees the connection concurrently, mutex_lock(&conn->lock) operates
> on freed memory. The existing NULL check is insufficient as it cannot
> prevent the connection from being freed after the check passes, and
> the early return also leaks the channel reference held by the timer.
>
> Fix by reading chan->conn under l2cap_chan_lock() and holding the
> connection with l2cap_conn_get(). After acquiring locks in the correct
> order (conn->lock then chan->lock), re-verify chan->conn in case
> l2cap_conn_del() already cleaned up the channel.
>
> Fixes: 3df91ea20e74 ("Bluetooth: Revert to mutexes from RCU list")
> Signed-off-by: Hyunwoo Kim <imv4bel@gmail.com>
> ---
> net/bluetooth/l2cap_core.c | 23 +++++++++++++++++++++--
> 1 file changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index abd091155d04..a432e94281dc 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -406,13 +406,20 @@ static void l2cap_chan_timeout(struct work_struct *work)
> {
> struct l2cap_chan *chan = container_of(work, struct l2cap_chan,
> chan_timer.work);
> - struct l2cap_conn *conn = chan->conn;
> + struct l2cap_conn *conn;
> int reason;
>
> BT_DBG("chan %p state %s", chan, state_to_string(chan->state));
>
> - if (!conn)
> + l2cap_chan_lock(chan);
> + conn = chan->conn;
> + if (!conn) {
> + l2cap_chan_unlock(chan);
> + l2cap_chan_put(chan);
> return;
> + }
> + l2cap_conn_get(conn);
> + l2cap_chan_unlock(chan);
>
> mutex_lock(&conn->lock);
> /* __set_chan_timer() calls l2cap_chan_hold(chan) while scheduling
> @@ -420,6 +427,17 @@ static void l2cap_chan_timeout(struct work_struct *work)
> */
> l2cap_chan_lock(chan);
>
> + /* Recheck since l2cap_conn_del() may have cleaned up the channel
> + * while we were waiting for conn->lock.
> + */
> + if (!chan->conn) {
> + l2cap_chan_unlock(chan);
> + l2cap_chan_put(chan);
> + mutex_unlock(&conn->lock);
> + l2cap_conn_put(conn);
> + return;
> + }
> +
> if (chan->state == BT_CONNECTED || chan->state == BT_CONFIG)
> reason = ECONNREFUSED;
> else if (chan->state == BT_CONNECT &&
> @@ -436,6 +454,7 @@ static void l2cap_chan_timeout(struct work_struct *work)
> l2cap_chan_put(chan);
>
> mutex_unlock(&conn->lock);
> + l2cap_conn_put(conn);
> }
>
> struct l2cap_chan *l2cap_chan_create(void)
> --
> 2.43.0
Actually maybe this is because we don't use cancel_delayed_work_sync
to wait for the work to complete on l2cap_chan_del, actually that
should use disable_delayed_work_sync to prevent the timer from being
rearmed, and that should be done to all the timers since l2cap_chan is
about to be destroyed.
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 4+ messages in thread* RE: Bluetooth: L2CAP: Fix use-after-free in l2cap_chan_timeout()
2026-03-19 15:14 [PATCH] Bluetooth: L2CAP: Fix use-after-free in l2cap_chan_timeout() Hyunwoo Kim
2026-03-19 15:55 ` Luiz Augusto von Dentz
@ 2026-03-19 16:36 ` bluez.test.bot
2026-04-09 20:01 ` bluez.test.bot
2 siblings, 0 replies; 4+ messages in thread
From: bluez.test.bot @ 2026-03-19 16:36 UTC (permalink / raw)
To: linux-bluetooth, imv4bel
[-- Attachment #1: Type: text/plain, Size: 2834 bytes --]
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=1069344
---Test result---
Test Summary:
CheckPatch PENDING 0.43 seconds
GitLint PENDING 0.35 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 25.02 seconds
CheckAllWarning PASS 27.79 seconds
CheckSparse PASS 26.74 seconds
BuildKernel32 PASS 24.54 seconds
TestRunnerSetup PASS 530.44 seconds
TestRunner_l2cap-tester PASS 27.95 seconds
TestRunner_iso-tester FAIL 31.28 seconds
TestRunner_bnep-tester PASS 6.51 seconds
TestRunner_mgmt-tester FAIL 112.54 seconds
TestRunner_rfcomm-tester PASS 9.59 seconds
TestRunner_sco-tester FAIL 14.31 seconds
TestRunner_ioctl-tester PASS 10.19 seconds
TestRunner_mesh-tester FAIL 12.46 seconds
TestRunner_smp-tester PASS 10.69 seconds
TestRunner_userchan-tester PASS 6.99 seconds
IncrementalBuild PENDING 0.80 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in le_read_features_complete+0x7e/0x2b0
Total: 141, Passed: 141 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.106 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
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.754 seconds
Mesh - Send cancel - 2 Timed out 2.000 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Bluetooth: L2CAP: Fix use-after-free in l2cap_chan_timeout()
2026-03-19 15:14 [PATCH] Bluetooth: L2CAP: Fix use-after-free in l2cap_chan_timeout() Hyunwoo Kim
2026-03-19 15:55 ` Luiz Augusto von Dentz
2026-03-19 16:36 ` bluez.test.bot
@ 2026-04-09 20:01 ` bluez.test.bot
2 siblings, 0 replies; 4+ messages in thread
From: bluez.test.bot @ 2026-04-09 20:01 UTC (permalink / raw)
To: linux-bluetooth, imv4bel
[-- Attachment #1: Type: text/plain, Size: 6877 bytes --]
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=1069344
---Test result---
Test Summary:
CheckPatch PENDING 0.73 seconds
GitLint PENDING 0.29 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 25.23 seconds
CheckAllWarning PASS 27.56 seconds
CheckSparse PASS 26.53 seconds
BuildKernel32 PASS 24.14 seconds
TestRunnerSetup PASS 539.17 seconds
TestRunner_l2cap-tester PASS 26.58 seconds
TestRunner_iso-tester PASS 43.33 seconds
TestRunner_bnep-tester PASS 5.97 seconds
TestRunner_mgmt-tester FAIL 110.68 seconds
TestRunner_rfcomm-tester PASS 9.05 seconds
TestRunner_sco-tester FAIL 13.94 seconds
TestRunner_ioctl-tester PASS 10.49 seconds
TestRunner_mesh-tester FAIL 11.48 seconds
TestRunner_smp-tester PASS 8.10 seconds
TestRunner_userchan-tester PASS 6.29 seconds
TestRunner_6lowpan-tester FAIL 8.29 seconds
IncrementalBuild PENDING 0.27 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.101 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
7.0.0-rc2-g8a3d4f6c0901 #1 Not tainted
------------------------------------------------------
kworker/u5:2/117 is trying to acquire lock:
ffff888002416240 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_connect_cfm+0x358/0x8d0
but task is already holding lock:
ffff8880025fc220 (&conn->lock){+.+.}-{3:3}, at: sco_connect_cfm+0x22d/0x8d0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&conn->lock){+.+.}-{3:3}:
lock_acquire+0xf7/0x2c0
_raw_spin_lock+0x2a/0x40
sco_sock_connect+0x4d7/0x1280
__sys_connect+0x1a3/0x260
__x64_sys_connect+0x6e/0xb0
do_syscall_64+0xa0/0x570
entry_SYSCALL_64_after_hwframe+0x74/0x7c
-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:
check_prev_add+0xe9/0xc70
__lock_acquire+0x1457/0x1df0
lock_acquire+0xf7/0x2c0
lock_sock_nested+0x36/0xd0
sco_connect_cfm+0x358/0x8d0
hci_sync_conn_complete_evt+0x3d3/0x8e0
hci_event_packet+0x74f/0xb10
hci_rx_work+0x398/0xd00
process_scheduled_works+0xb16/0x1ac0
worker_thread+0x4ff/0xba0
kthread+0x368/0x490
ret_from_fork+0x498/0x7e0
ret_from_fork_asm+0x19/0x30
other info that might help us debug this:
...
BUG: sleeping function called from invalid context at net/core/sock.c:3782
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 117, name: kworker/u5:2
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
INFO: lockdep is turned off.
CPU: 0 UID: 0 PID: 117 Comm: kworker/u5:2 Not tainted 7.0.0-rc2-g8a3d4f6c0901 #1 PREEMPT(lazy)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
Workqueue: hci0 hci_rx_work
Call Trace:
<TASK>
dump_stack_lvl+0x49/0x60
__might_resched+0x2ea/0x500
lock_sock_nested+0x47/0xd0
? sco_connect_cfm+0x358/0x8d0
sco_connect_cfm+0x358/0x8d0
? hci_debugfs_create_conn+0x190/0x210
? __pfx_sco_connect_cfm+0x10/0x10
hci_sync_conn_complete_evt+0x3d3/0x8e0
hci_event_packet+0x74f/0xb10
? __pfx_hci_sync_conn_complete_evt+0x10/0x10
? __pfx_hci_event_packet+0x10/0x10
? mark_held_locks+0x49/0x80
? lockdep_hardirqs_on_prepare+0xd4/0x180
? _raw_spin_unlock_irqrestore+0x2c/0x50
hci_rx_work+0x398/0xd00
process_scheduled_works+0xb16/0x1ac0
? __pfx_process_scheduled_works+0x10/0x10
? lock_acquire+0xf7/0x2c0
? lock_is_held_type+0x9b/0x110
? __pfx_hci_rx_work+0x10/0x10
worker_thread+0x4ff/0xba0
? _raw_spin_unlock_irqrestore+0x2c/0x50
? __pfx_worker_thread+0x10/0x10
kthread+0x368/0x490
? _raw_spin_unlock_irq+0x23/0x40
? __pfx_kthread+0x10/0x10
ret_from_fork+0x498/0x7e0
? __pfx_ret_from_fork+0x10/0x10
? __switch_to+0x9e4/0xe50
? __switch_to_asm+0x32/0x60
...
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
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.258 seconds
Mesh - Send cancel - 2 Timed out 1.995 seconds
##############################
Test: TestRunner_6lowpan-tester - FAIL
Desc: Run 6lowpan-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
7.0.0-rc2-g8a3d4f6c0901 #1 Not tainted
------------------------------------------------------
kworker/0:1/11 is trying to acquire lock:
ffff8880026e0940 ((wq_completion)hci0#2){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x75/0x180
but task is already holding lock:
ffffffffb5c4d720 (rtnl_mutex){+.+.}-{4:4}, at: lowpan_unregister_netdev+0xd/0x30
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #4 (rtnl_mutex){+.+.}-{4:4}:
lock_acquire+0xf7/0x2c0
__mutex_lock+0x16b/0x1fc0
lowpan_register_netdev+0x11/0x30
chan_ready_cb+0x836/0xd00
l2cap_recv_frame+0x6a06/0x8920
l2cap_recv_acldata+0x790/0xdf0
hci_rx_work+0x500/0xd00
process_scheduled_works+0xb16/0x1ac0
worker_thread+0x4ff/0xba0
kthread+0x368/0x490
ret_from_fork+0x498/0x7e0
ret_from_fork_asm+0x19/0x30
-> #3 (&chan->lock#3/1){+.+.}-{4:4}:
lock_acquire+0xf7/0x2c0
__mutex_lock+0x16b/0x1fc0
l2cap_chan_connect+0x74e/0x1980
lowpan_control_write+0x523/0x660
full_proxy_write+0x10b/0x190
vfs_write+0x1c0/0xf60
ksys_write+0xf1/0x1d0
do_syscall_64+0xa0/0x570
entry_SYSCALL_64_after_hwframe+0x74/0x7c
-> #2 (&conn->lock){+.+.}-{4:4}:
...
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
https://github.com/bluez/bluetooth-next/pull/24/checks
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 4+ messages in thread