general protection fault in __queue_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 14b58326 Linux 4.14.193
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=106642aa900000
kernel config: https://syzkaller.appspot.com/x/.config?x=68ef0287ccbc3b42
dashboard link: https://syzkaller.appspot.com/bug?extid=920d77b97cf789b3113e
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1367322c900000

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

NOHZ: local_softirq_pending 08
NOHZ: local_softirq_pending 08
Bluetooth: hci3 command 0x0419 tx timeout
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 20544 Comm: syz-executor.2 Not tainted 4.14.193-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880845804c0 task.stack: ffff88809b640000
RIP: 0010:__queue_work+0x153/0xf70 kernel/workqueue.c:1406
RSP: 0018:ffff88809b647970 EFLAGS: 00010046
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000005 RDI: ffffffff87d56680
RBP: 0000000000000000 R08: ffffffff8a762388 R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880845804c0 R12: dffffc0000000000
R13: ffff8880a4161940 R14: ffff8880a78c4040 R15: ffff888090731cc0
FS: 00007f3086ddd700(0000) GS:ffff8880aea00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055d2f6ae7918 CR3: 000000009222a000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
queue_work_on+0x159/0x1d0 kernel/workqueue.c:1490
queue_work include/linux/workqueue.h:491 [inline]
req_run+0x2bb/0x490 net/bluetooth/hci_request.c:77
hci_req_run_skb net/bluetooth/hci_request.c:89 [inline]
__hci_req_sync+0x277/0x770 net/bluetooth/hci_request.c:214
hci_req_sync+0x71/0xa0 net/bluetooth/hci_request.c:285
hci_inquiry+0x5e1/0x810 net/bluetooth/hci_core.c:1272
hci_sock_ioctl+0x15a/0x650 net/bluetooth/hci_sock.c:1043
sock_do_ioctl net/socket.c:974 [inline]
sock_ioctl+0x2cc/0x4c0 net/socket.c:1071
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45ce79
RSP: 002b:00007f3086ddcc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000000e640 RCX: 000000000045ce79
RDX: 0000000020000000 RSI: 00000000800448f0 RDI: 0000000000000005
RBP: 000000000118c0a0 R08: 0000000000000000 R09: 0000000000000000
Bluetooth: hci2 command 0x0409 tx timeout
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118c06c
R13: 00007ffdad0b90df R14: 00007f3086ddd9c0 R15: 000000000118c06c
Code: 7a ff ff 48 89 c5 e8 7d 3b 20 00 4c 89 ef e8 85 cb ff ff 48 85 c0 49 89 c6 0f 84 43 04 00 00 e8 64 3b 20 00 48 89 e8 48 c1 e8 03 <42> 80 3c 20 00 0f 85 4c 0c 00 00 4c 39 75 00 0f 84 3d 04 00 00
RIP: __queue_work+0x153/0xf70 kernel/workqueue.c:1406 RSP: ffff88809b647970
---[ end trace 5cac06de6fc44092 ]---


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches