general protection fault in ioctl

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 830a059c Linux 4.19.186
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=164a479ad00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7415cc95f9edb7b9
dashboard link: https://syzkaller.appspot.com/bug?extid=218a082141f9d0064522

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

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

vt_ioctl+0xd29/0x2380 drivers/tty/vt/vt_ioctl.c:575
vhci_hcd: release socket
kasan: CONFIG_KASAN_INLINE enabled
tty_ioctl+0x5b0/0x15c0 drivers/tty/tty_io.c:2669
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 9174 Comm: syz-executor.0 Not tainted 4.19.186-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__lock_acquire+0x1eb/0x3ff0 kernel/locking/lockdep.c:3294
Code: 2b 29 00 00 48 81 c4 98 01 00 00 44 89 f8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f 85 b3 2a 00 00 49 81 3e 20 d2 66 8c 0f 84 65 ff ff
RSP: 0018:ffff8882340e77d0 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 00000000000000fc RSI: 0000000000000000 RDI: 0000000000000001
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000001
R13: ffff8880ab8b0380 R14: 00000000000007e0 R15: 0000000000000001
FS: 00007fa9349f8700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f789467e920 CR3: 000000022d99d000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x466459
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f50c78c9188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000466459
RDX: 0000000020000440 RSI: 0000000000004b31 RDI: 0000000000000003
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907
RBP: 00007f50c78c91d0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x8c/0xc0 kernel/locking/spinlock.c:152
R13: 00007ffe8fa6f80f R14: 00007f50c78c9300 R15: 0000000000022000
vhci_hcd: disconnect device
try_to_wake_up+0x7b/0x1050 kernel/sched/core.c:1961
attach_store+0x65b/0xaa0 drivers/usb/usbip/vhci_sysfs.c:421
dev_attr_store+0x56/0x80 drivers/base/core.c:966
sysfs_kf_write+0x110/0x160 fs/sysfs/file.c:140
kernfs_fop_write+0x2b0/0x470 fs/kernfs/file.c:316
__vfs_write+0xf7/0x770 fs/read_write.c:485
vfs_write+0x1f3/0x540 fs/read_write.c:549
ksys_write+0x12b/0x2a0 fs/read_write.c:599
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x41913f
Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 99 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 cc fd ff ff 48
RSP: 002b:00007fa9349f7b90 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 000000000041913f
RDX: 0000000000000007 RSI: 00007fa9349f7be0 RDI: 0000000000000005
RBP: 0000000000000005 R08: 0000000000000000 R09: 00007fa9349f7b30
R10: 0000000000000000 R11: 0000000000000293 R12: 00000000004afb38
R13: 00007fa9349f7be0 R14: 0000000000000000 R15: 0000000000022000
Modules linked in:
---[ end trace 4e481da2ed19cf43 ]---
RIP: 0010:__lock_acquire+0x1eb/0x3ff0 kernel/locking/lockdep.c:3294
Code: 2b 29 00 00 48 81 c4 98 01 00 00 44 89 f8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f 85 b3 2a 00 00 49 81 3e 20 d2 66 8c 0f 84 65 ff ff
RSP: 0018:ffff8882340e77d0 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 00000000000000fc RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000001
R13: ffff8880ab8b0380 R14: 00000000000007e0 R15: 0000000000000001
FS: 00007fa9349f8700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f789467e920 CR3: 000000022d99d000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.