* Re: [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_close
[not found] <20260913015111.82827-1-jcperdomo100@gmail.com>
@ 2026-09-13 2:16 ` syzbot
0 siblings, 0 replies; 3+ messages in thread
From: syzbot @ 2026-09-13 2:16 UTC (permalink / raw)
To: jcperdomo100, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0cece8fa7d83523f47a3@syzkaller.appspotmail.com
Tested-by: syzbot+0cece8fa7d83523f47a3@syzkaller.appspotmail.com
Tested on:
commit: 2f0c1cf7 Merge tag 's390-7.3-3' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=136ca925580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
dashboard link: https://syzkaller.appspot.com/bug?extid=0cece8fa7d83523f47a3
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=17889905580000
Note: testing is done by a robot and is best-effort only.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_close
[not found] <20260912204938.30062-1-jcperdomo100@gmail.com>
@ 2026-09-12 21:04 ` syzbot
0 siblings, 0 replies; 3+ messages in thread
From: syzbot @ 2026-09-12 21:04 UTC (permalink / raw)
To: jcperdomo100, linux-kernel, syzkaller-bugs
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KASAN: slab-use-after-free Read in bt_accept_unlink
==================================================================
BUG: KASAN: slab-use-after-free in __raw_spin_lock_bh include/linux/spinlock_api_smp.h:182 [inline]
BUG: KASAN: slab-use-after-free in _raw_spin_lock_bh+0x33/0x40 kernel/locking/spinlock.c:205
Read of size 1 at addr ffff8880553d85a0 by task krfcommd/3367
CPU: 0 UID: 0 PID: 3367 Comm: krfcommd Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
print_address_description mm/kasan/report.c:378 [inline]
print_report+0x13d/0x4b0 mm/kasan/report.c:482
kasan_report+0xdf/0x1c0 mm/kasan/report.c:595
__kasan_check_byte+0x36/0x50 mm/kasan/common.c:574
kasan_check_byte include/linux/kasan.h:402 [inline]
lock_acquire kernel/locking/lockdep.c:5916 [inline]
lock_acquire+0x132/0x380 kernel/locking/lockdep.c:5899
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:182 [inline]
_raw_spin_lock_bh+0x33/0x40 kernel/locking/spinlock.c:205
spin_lock_bh include/linux/spinlock.h:353 [inline]
bt_accept_unlink+0x64/0x370 net/bluetooth/af_bluetooth.c:263
rfcomm_sk_state_change+0x319/0x3d0 net/bluetooth/rfcomm/sock.c:83
__rfcomm_dlc_close.isra.0+0x1e3/0x750 net/bluetooth/rfcomm/core.c:490
rfcomm_session_close.isra.0+0xd5/0x190 net/bluetooth/rfcomm/core.c:753
rfcomm_process_rx net/bluetooth/rfcomm/core.c:2029 [inline]
rfcomm_process_sessions net/bluetooth/rfcomm/core.c:2114 [inline]
rfcomm_run+0x6dd/0x54c0 net/bluetooth/rfcomm/core.c:2204
kthread+0x373/0x450 kernel/kthread.c:436
ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Allocated by task 7393:
kasan_save_stack+0x30/0x50 mm/kasan/common.c:57
kasan_save_track+0x14/0x30 mm/kasan/common.c:78
poison_kmalloc_redzone mm/kasan/common.c:398 [inline]
__kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:415
kasan_kmalloc include/linux/kasan.h:263 [inline]
__do_kmalloc_node mm/slub.c:5414 [inline]
__kmalloc_noprof+0x32f/0x840 mm/slub.c:5439
_kmalloc_noprof include/linux/slab.h:995 [inline]
sk_prot_alloc+0x10b/0x2a0 net/core/sock.c:2251
sk_alloc+0x36/0xe80 net/core/sock.c:2307
bt_sock_alloc+0x3b/0x3c0 net/bluetooth/af_bluetooth.c:148
rfcomm_sock_alloc.constprop.0+0x51/0x2a0 net/bluetooth/rfcomm/sock.c:290
rfcomm_sock_create+0xf1/0x180 net/bluetooth/rfcomm/sock.c:328
bt_sock_create+0x185/0x350 net/bluetooth/af_bluetooth.c:132
__sock_create+0x339/0x860 net/socket.c:1676
sock_create net/socket.c:1734 [inline]
__sys_socket_create net/socket.c:1771 [inline]
__sys_socket+0x14d/0x260 net/socket.c:1818
__do_sys_socket net/socket.c:1832 [inline]
__se_sys_socket net/socket.c:1830 [inline]
__x64_sys_socket+0x72/0xb0 net/socket.c:1830
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Freed by task 7392:
kasan_save_stack+0x30/0x50 mm/kasan/common.c:57
kasan_save_track+0x14/0x30 mm/kasan/common.c:78
kasan_save_free_info+0x3b/0x70 mm/kasan/generic.c:584
poison_slab_object mm/kasan/common.c:253 [inline]
__kasan_slab_free+0x5f/0x80 mm/kasan/common.c:285
kasan_slab_free include/linux/kasan.h:235 [inline]
slab_free_hook mm/slub.c:2748 [inline]
slab_free mm/slub.c:6508 [inline]
kfree+0x22b/0x6d0 mm/slub.c:6801
sk_prot_free net/core/sock.c:2290 [inline]
__sk_destruct+0x88c/0xab0 net/core/sock.c:2390
sk_destruct+0xc8/0xf0 net/core/sock.c:2418
__sk_free+0xf4/0x3e0 net/core/sock.c:2429
sk_free+0x61/0x90 net/core/sock.c:2440
sock_put include/net/sock.h:2020 [inline]
rfcomm_sock_kill net/bluetooth/rfcomm/sock.c:213 [inline]
rfcomm_sock_kill+0x12b/0x230 net/bluetooth/rfcomm/sock.c:203
rfcomm_sock_release+0x119/0x1a0 net/bluetooth/rfcomm/sock.c:942
__sock_release+0xb3/0x260 net/socket.c:735
sock_close+0x1c/0x30 net/socket.c:1526
__fput+0x3ff/0xb50 fs/file_table.c:512
task_work_run+0x150/0x240 kernel/task_work.c:233
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
__exit_to_user_mode_loop kernel/entry/common.c:70 [inline]
exit_to_user_mode_loop+0x1d8/0x700 kernel/entry/common.c:101
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:336 [inline]
do_syscall_64+0x661/0x790 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
The buggy address belongs to the object at ffff8880553d8000
which belongs to the cache kmalloc-2k of size 2048
The buggy address is located 1440 bytes inside of
freed 2048-byte region [ffff8880553d8000, ffff8880553d8800)
The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff8880553dd000 pfn:0x553d8
head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0
flags: 0xfff00000000240(workingset|head|node=0|zone=1|lastcpupid=0x7ff)
page_type: f5(slab)
raw: 00fff00000000240 ffff88801c042f00 ffffea0000d5a810 ffffea0000d83610
raw: ffff8880553dd000 0000000000080005 00000000f5000000 0000000000000000
head: 00fff00000000240 ffff88801c042f00 ffffea0000d5a810 ffffea0000d83610
head: ffff8880553dd000 0000000000080005 00000000f5000000 0000000000000000
head: 00fff00000000003 fffffffffffffe01 00000000ffffffff 00000000ffffffff
head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000008
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 6186, tgid 6186 (syz-executor), ts 85585809850
set_page_owner include/linux/page_owner.h:33 [inline]
post_alloc_hook+0xfd/0x120 mm/page_alloc.c:1871
prep_new_page mm/page_alloc.c:1879 [inline]
get_page_from_freelist+0x110d/0x35d0 mm/page_alloc.c:3943
__alloc_frozen_pages_noprof+0x2eb/0x3300 mm/page_alloc.c:5436
alloc_slab_page mm/slub.c:3347 [inline]
allocate_slab mm/slub.c:3462 [inline]
new_slab+0xa9/0x6e0 mm/slub.c:3513
refill_objects+0xe3/0x410 mm/slub.c:7417
refill_sheaf mm/slub.c:2885 [inline]
__pcs_replace_empty_main+0x35e/0x650 mm/slub.c:4774
alloc_from_pcs mm/slub.c:4850 [inline]
slab_alloc_node mm/slub.c:4984 [inline]
__kmalloc_cache_noprof+0x4f4/0x6d0 mm/slub.c:5559
_kmalloc_noprof include/linux/slab.h:991 [inline]
_kzalloc_noprof include/linux/slab.h:1312 [inline]
rxrpc_alloc_connection+0xa3/0x770 net/rxrpc/conn_object.c:62
rxrpc_prealloc_service_connection+0x26/0x390 net/rxrpc/conn_service.c:123
rxrpc_service_prealloc_one+0x2c5/0x1040 net/rxrpc/call_accept.c:86
rxrpc_kernel_charge_accept+0xdd/0x120 net/rxrpc/call_accept.c:489
afs_charge_preallocation+0xd8/0x360 fs/afs/rxrpc.c:766
afs_open_socket+0x31e/0x3f0 fs/afs/rxrpc.c:112
afs_net_init+0x825/0xb00 fs/afs/main.c:116
ops_init+0x1e2/0x5f0 net/core/net_namespace.c:137
setup_net+0x118/0x3a0 net/core/net_namespace.c:443
page last free pid 6013 tgid 6003 ts 80477321559 stack trace:
reset_page_owner include/linux/page_owner.h:26 [inline]
__free_pages_prepare mm/page_alloc.c:1418 [inline]
__free_frozen_pages+0x79f/0x10f0 mm/page_alloc.c:2962
__folio_put+0x3b4/0x5f0 mm/folio.c:105
folio_put include/linux/mm.h:2160 [inline]
put_page include/linux/mm.h:2229 [inline]
put_netmem include/net/netmem.h:394 [inline]
skb_page_unref include/linux/skbuff_ref.h:43 [inline]
__skb_frag_unref include/linux/skbuff_ref.h:56 [inline]
skb_release_data+0x649/0x8e0 net/core/skbuff.c:1116
skb_release_all net/core/skbuff.c:1197 [inline]
__napi_kfree_skb net/core/skbuff.c:1494 [inline]
kfree_skb_napi_cache net/core/skbuff.c:7313 [inline]
skb_attempt_defer_free+0x2ed/0x830 net/core/skbuff.c:7346
tcp_eat_recv_skb net/ipv4/tcp.c:1621 [inline]
tcp_recvmsg_locked+0x11ed/0x2a30 net/ipv4/tcp.c:2899
tcp_recvmsg+0x141/0x630 net/ipv4/tcp.c:2944
inet6_recvmsg+0xd5/0x4c0 net/ipv6/af_inet6.c:656
sock_recvmsg_nosec net/socket.c:1151 [inline]
sock_recvmsg+0x102/0x220 net/socket.c:1173
sock_read_iter+0x2b0/0x3a0 net/socket.c:1242
new_sync_read fs/read_write.c:493 [inline]
vfs_read+0x960/0xb40 fs/read_write.c:574
ksys_read+0x1f8/0x250 fs/read_write.c:716
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Memory state around the buggy address:
ffff8880553d8480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8880553d8500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff8880553d8580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8880553d8600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8880553d8680: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
Tested on:
commit: cba2348a Merge tag 'xfs-fixes-7.3-rc3' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16eb2925580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
dashboard link: https://syzkaller.appspot.com/bug?extid=0cece8fa7d83523f47a3
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=13371905580000
^ permalink raw reply [flat|nested] 3+ messages in thread
* [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_close
@ 2026-09-10 16:09 syzbot
0 siblings, 0 replies; 3+ messages in thread
From: syzbot @ 2026-09-10 16:09 UTC (permalink / raw)
To: linux-bluetooth, linux-kernel, luiz.dentz, marcel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 50d05c7c76c9 Merge tag 'landlock-7.3-rc3' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15ad0905580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
dashboard link: https://syzkaller.appspot.com/bug?extid=0cece8fa7d83523f47a3
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13ad0905580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12752c8e580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-50d05c7c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6f77d29903f3/vmlinux-50d05c7c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23b2961d9c5d/bzImage-50d05c7c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0cece8fa7d83523f47a3@syzkaller.appspotmail.com
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.67/5982 is trying to acquire lock:
ffffffff90f80f40 (rfcomm_mutex){+.+.}-{4:4}, at: rfcomm_dlc_close+0x33/0x240 net/bluetooth/rfcomm/core.c:508
but task is already holding lock:
ffff8880234b9260 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1713 [inline]
ffff8880234b9260 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sock_close net/bluetooth/rfcomm/sock.c:245 [inline]
ffff8880234b9260 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sock_cleanup_listen net/bluetooth/rfcomm/sock.c:190 [inline]
ffff8880234b9260 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: __rfcomm_sock_close+0x1c3/0x300 net/bluetooth/rfcomm/sock.c:224
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}:
lock_acquire kernel/locking/lockdep.c:5942 [inline]
lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
lock_sock_nested+0x41/0xf0 net/core/sock.c:3830
lock_sock include/net/sock.h:1713 [inline]
rfcomm_connect_ind+0x327/0x9e0 net/bluetooth/rfcomm/sock.c:968
rfcomm_recv_pn net/bluetooth/rfcomm/core.c:1509 [inline]
rfcomm_recv_mcc net/bluetooth/rfcomm/core.c:1727 [inline]
rfcomm_recv_frame net/bluetooth/rfcomm/core.c:1868 [inline]
rfcomm_process_rx net/bluetooth/rfcomm/core.c:2020 [inline]
rfcomm_process_sessions net/bluetooth/rfcomm/core.c:2114 [inline]
rfcomm_run+0x438b/0x54c0 net/bluetooth/rfcomm/core.c:2204
kthread+0x373/0x450 kernel/kthread.c:436
ret_from_fork+0x730/0xd60 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
-> #0 (rfcomm_mutex){+.+.}-{4:4}:
check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3209
check_prevs_add kernel/locking/lockdep.c:3328 [inline]
validate_chain kernel/locking/lockdep.c:3952 [inline]
__lock_acquire+0x1528/0x1f40 kernel/locking/lockdep.c:5288
lock_acquire kernel/locking/lockdep.c:5942 [inline]
lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
__mutex_lock_common kernel/locking/mutex.c:646 [inline]
__mutex_lock+0x1a4/0x1bd0 kernel/locking/mutex.c:821
rfcomm_dlc_close+0x33/0x240 net/bluetooth/rfcomm/core.c:508
__rfcomm_sock_close+0x181/0x300 net/bluetooth/rfcomm/sock.c:231
rfcomm_sock_close net/bluetooth/rfcomm/sock.c:246 [inline]
rfcomm_sock_cleanup_listen net/bluetooth/rfcomm/sock.c:190 [inline]
__rfcomm_sock_close+0x1d2/0x300 net/bluetooth/rfcomm/sock.c:224
rfcomm_sock_shutdown+0x111/0x250 net/bluetooth/rfcomm/sock.c:920
rfcomm_sock_release+0x61/0x1a0 net/bluetooth/rfcomm/sock.c:941
__sock_release+0xb3/0x260 net/socket.c:735
sock_close+0x1c/0x30 net/socket.c:1526
__fput+0x3ff/0xb50 fs/file_table.c:512
task_work_run+0x150/0x240 kernel/task_work.c:233
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
__exit_to_user_mode_loop kernel/entry/common.c:70 [inline]
exit_to_user_mode_loop+0x1d8/0x700 kernel/entry/common.c:101
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:336 [inline]
do_syscall_64+0x661/0x790 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM);
lock(rfcomm_mutex);
lock(sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM);
lock(rfcomm_mutex);
*** DEADLOCK ***
locks held by syz.0.67/5982: 2, last CPU#0:
#0: ffff88805501bbc0 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
#0: ffff88805501bbc0 (&sb->s_type->i_mutex_key#13){+.+.}-{4:4}, at: __sock_release+0x86/0x260 net/socket.c:734
#1: ffff8880234b9260 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1713 [inline]
#1: ffff8880234b9260 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sock_close net/bluetooth/rfcomm/sock.c:245 [inline]
#1: ffff8880234b9260 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sock_cleanup_listen net/bluetooth/rfcomm/sock.c:190 [inline]
#1: ffff8880234b9260 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: __rfcomm_sock_close+0x1c3/0x300 net/bluetooth/rfcomm/sock.c:224
stack backtrace:
CPU: 0 UID: 0 PID: 5982 Comm: syz.0.67 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
print_circular_bug.cold+0x178/0x1be kernel/locking/lockdep.c:2087
check_noncircular+0x146/0x160 kernel/locking/lockdep.c:2219
check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3209
check_prevs_add kernel/locking/lockdep.c:3328 [inline]
validate_chain kernel/locking/lockdep.c:3952 [inline]
__lock_acquire+0x1528/0x1f40 kernel/locking/lockdep.c:5288
lock_acquire kernel/locking/lockdep.c:5942 [inline]
lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5899
__mutex_lock_common kernel/locking/mutex.c:646 [inline]
__mutex_lock+0x1a4/0x1bd0 kernel/locking/mutex.c:821
rfcomm_dlc_close+0x33/0x240 net/bluetooth/rfcomm/core.c:508
__rfcomm_sock_close+0x181/0x300 net/bluetooth/rfcomm/sock.c:231
rfcomm_sock_close net/bluetooth/rfcomm/sock.c:246 [inline]
rfcomm_sock_cleanup_listen net/bluetooth/rfcomm/sock.c:190 [inline]
__rfcomm_sock_close+0x1d2/0x300 net/bluetooth/rfcomm/sock.c:224
rfcomm_sock_shutdown+0x111/0x250 net/bluetooth/rfcomm/sock.c:920
rfcomm_sock_release+0x61/0x1a0 net/bluetooth/rfcomm/sock.c:941
__sock_release+0xb3/0x260 net/socket.c:735
sock_close+0x1c/0x30 net/socket.c:1526
__fput+0x3ff/0xb50 fs/file_table.c:512
task_work_run+0x150/0x240 kernel/task_work.c:233
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
__exit_to_user_mode_loop kernel/entry/common.c:70 [inline]
exit_to_user_mode_loop+0x1d8/0x700 kernel/entry/common.c:101
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:336 [inline]
do_syscall_64+0x661/0x790 arch/x86/entry/syscall_64.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd18819e159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe0b172838 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007ffe0b172920 RCX: 00007fd18819e159
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 000000000000e138 R08: 0000000000000001 R09: 0000000000000000
R10: 0000001b32a20000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd188425fac R14: 00007fd188425fa8 R15: 00007fd188425fa0
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-09-13 2:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20260913015111.82827-1-jcperdomo100@gmail.com>
2026-09-13 2:16 ` [syzbot] [bluetooth?] possible deadlock in rfcomm_dlc_close syzbot
[not found] <20260912204938.30062-1-jcperdomo100@gmail.com>
2026-09-12 21:04 ` syzbot
2026-09-10 16:09 syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®