linux-kernel - [syzbot] [bluetooth?] WARNING in l2cap_send

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <000000000000919a9b061dfb239a@google.com>
Date: Wed, 24 Jul 2024 02:45:30 -0700
From: syzbot <syzbot+d87defb553e002cd88a5@...kaller.appspotmail.com>
To: johan.hedberg@...il.com, linux-bluetooth@...r.kernel.org, 
	linux-kernel@...r.kernel.org, luiz.dentz@...il.com, marcel@...tmann.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [bluetooth?] WARNING in l2cap_send_cmd

Hello,

syzbot found the following issue on:

HEAD commit:    933069701c1b Merge tag '6.11-rc-smb3-server-fixes' of git:..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1052d5c3980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=bc5806b0bf399dd9
dashboard link: https://syzkaller.appspot.com/bug?extid=d87defb553e002cd88a5
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-93306970.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/669de3c5a584/vmlinux-93306970.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6fb52aed0488/bzImage-93306970.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d87defb553e002cd88a5@...kaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 8 at kernel/workqueue.c:2259 __queue_work+0xc2b/0x1070 kernel/workqueue.c:2258
Modules linked in:
CPU: 0 UID: 0 PID: 8 Comm: kworker/0:0 Not tainted 6.10.0-syzkaller-11840-g933069701c1b #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Workqueue: events l2cap_chan_timeout
RIP: 0010:__queue_work+0xc2b/0x1070 kernel/workqueue.c:2258
Code: 07 83 c0 03 38 d0 7c 09 84 d2 74 05 e8 be 59 93 00 8b 5b 2c 31 ff 83 e3 20 89 de e8 8f c1 34 00 85 db 75 60 e8 86 c6 34 00 90 <0f> 0b 90 e9 08 f8 ff ff e8 78 c6 34 00 90 0f 0b 90 e9 b7 f7 ff ff
RSP: 0018:ffffc900003a7a20 EFLAGS: 00010093
RAX: 0000000000000000 RBX: ffff8880154a0000 RCX: ffffffff8158184a
RDX: ffff888015f22440 RSI: ffffffff8156553a RDI: ffff8880154a0008
RBP: ffff888020da0b10 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000200000 R11: 000000000000000f R12: 0000000000000000
R13: 0000000000000008 R14: ffff888011aba000 R15: ffff888011aba000
FS:  0000000000000000(0000) GS:ffff88802c000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000f331a0f8 CR3: 000000001d234000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 queue_work_on+0x11a/0x140 kernel/workqueue.c:2392
 l2cap_send_cmd+0x6db/0x920 net/bluetooth/l2cap_core.c:973
 l2cap_send_disconn_req+0x1f4/0x410 net/bluetooth/l2cap_core.c:1487
 l2cap_chan_close+0x2df/0xa30 net/bluetooth/l2cap_core.c:826
 l2cap_chan_timeout+0x196/0x310 net/bluetooth/l2cap_core.c:435
 process_one_work+0x958/0x1ad0 kernel/workqueue.c:3231
 process_scheduled_works kernel/workqueue.c:3312 [inline]
 worker_thread+0x6c8/0xf20 kernel/workqueue.c:3390
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </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@...glegroups.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 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