syzbot


INFO: task hung in vt_ioctl (7)

Status: auto-obsoleted due to no activity on 2026/07/14 12:03
Subsystems: kernel
Labels: prio:high
[Documentation on labels]
First crash: 95d, last: 91d
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision Error
2f145eae-565b-4ec1-af80-5fc7d6d18447 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ INFO: task hung in vt_ioctl (7) 2026/05/30 06:14 2026/05/30 06:14 2026/05/30 07:07 6b4a844333e83556da95d61d7f207e7ef5cd4bc6

			
		
250cad9a-e081-4a0d-879b-5f62272b85e7 assessment-security 💥 INFO: task hung in vt_ioctl (7) 2026/05/14 08:18 2026/05/14 08:18 2026/05/14 08:19 6ccb967e465e832a7bfd7a116ad00d52a0923a5d
failed to run ["git" "pull" "origin" "HEAD" "--depth=1" "--allow-unrelated-histories"]: exit status 128
From /app/workdir/repo/linux
 * branch                HEAD       -> FETCH_HEAD
Updating files:  ...
truncated to first 200 bytes; open job for full error
Similar bugs (8)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 INFO: task hung in vt_ioctl 1 1 255d 255d 0/2 auto-obsoleted due to no activity on 2026/02/10 14:54
upstream INFO: task hung in vt_ioctl (4) serial 1 1 1030d 1030d 0/29 auto-obsoleted due to no activity on 2023/12/19 05:20
upstream INFO: task hung in vt_ioctl (6) kernel 1 1 332d 332d 0/29 auto-obsoleted due to no activity on 2025/11/16 03:48
linux-4.19 INFO: task hung in vt_ioctl 1 1 2240d 2240d 0/1 auto-closed as invalid on 2020/09/24 20:12
upstream INFO: task hung in vt_ioctl (3) serial 1 1 1209d 1209d 0/29 auto-obsoleted due to no activity on 2023/06/22 09:16
upstream INFO: task hung in vt_ioctl serial 1 1 2334d 2334d 0/29 auto-closed as invalid on 2020/05/23 20:53
upstream INFO: task hung in vt_ioctl (2) serial 1 2 2203d 2242d 0/29 auto-closed as invalid on 2020/10/01 08:58
upstream INFO: task hung in vt_ioctl (5) kernel 1 1 494d 494d 0/29 auto-obsoleted due to no activity on 2025/06/06 19:57

Sample crash report:
INFO: task syz.4.7854:29524 blocked for more than 143 seconds.
      Tainted: G             L      syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.7854      state:D stack:28792 pid:29524 tgid:29522 ppid:19985  task_flags:0x400140 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5382 [inline]
 __schedule+0x10e9/0x6820 kernel/sched/core.c:7183
 __schedule_loop kernel/sched/core.c:7262 [inline]
 schedule+0xdd/0x390 kernel/sched/core.c:7277
 schedule_timeout+0x1b2/0x280 kernel/time/sleep_timeout.c:75
 ___down_common kernel/locking/semaphore.c:289 [inline]
 __down_common+0x371/0x8a0 kernel/locking/semaphore.c:314
 down+0x74/0xa0 kernel/locking/semaphore.c:100
 console_lock+0x5b/0xa0 kernel/printk/printk.c:2896
 class_console_lock_constructor include/linux/console.h:736 [inline]
 vt_disallocate drivers/tty/vt/vt_ioctl.c:630 [inline]
 vt_ioctl+0x1d33/0x31a0 drivers/tty/vt/vt_ioctl.c:891
 tty_ioctl+0x26a/0x1640 drivers/tty/tty_io.c:2792
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl fs/ioctl.c:583 [inline]
 __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x10b/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f333c59c819
RSP: 002b:00007f333d37c028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f333c816090 RCX: 00007f333c59c819
RDX: 0000000000000001 RSI: 0000000000005608 RDI: 0000000000000004
RBP: 00007f333c632c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f333c816128 R14: 00007f333c816090 R15: 00007ffd31cccc98
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8e7e70a0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8e7e70a0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline]
 #0: ffffffff8e7e70a0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x3d/0x184 kernel/locking/lockdep.c:6775
2 locks held by kworker/u8:10/1160:
 #0: ffff88801e794940 ((wq_completion)iou_exit){+.+.}-{0:0}, at: process_one_work+0x12d6/0x1980 kernel/workqueue.c:3263
 #1: ffffc9000578fd08 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x973/0x1980 kernel/workqueue.c:3264
2 locks held by kworker/0:6/5910:
2 locks held by kworker/u8:4/13687:
 #0: ffff88813feac940 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_one_work+0x12d6/0x1980 kernel/workqueue.c:3263
 #1: ffffc90003617d08 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x973/0x1980 kernel/workqueue.c:3264
2 locks held by getty/28771:
 #0: ffff8880375f70a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc90003a172e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x419/0x14f0 drivers/tty/n_tty.c:2211
2 locks held by syz.3.7660/28797:
 #0: ffffffff906caa08 (cb_lock){++++}-{4:4}, at: genl_rcv+0x19/0x40 net/netlink/genetlink.c:1217
 #1: ffffffff8ec5f820 (nfsd_mutex){+.+.}-{4:4}, at: nfsd_nl_listener_set_doit+0xd5/0x1a80 fs/nfsd/nfsctl.c:1903
6 locks held by syz.4.7854/29523:
2 locks held by syz.1.7881/29676:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
 #1: ffff888065a391b0 (&tty->legacy_mutex){+.+.}-{4:4}, at: tty_init_dev.part.0+0x39/0x470 drivers/tty/tty_io.c:1406
1 lock held by syz.1.7881/29680:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.6.7896/29714:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.6.7896/29716:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.5.7897/29717:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.2.7901/29731:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.9.7921/29914:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.8.7935/29966:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.0.7950/30026:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.7.7952/30033:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.3.7968/30152:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.1.7970/30192:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
2 locks held by syz.6.7973/30204:
 #0: ffff88807a2260d8 (&type->s_umount_key#55/1){+.+.}-{4:4}, at: alloc_super+0x244/0xd20 fs/super.c:345
 #1: ffffffff8ec5f820 (nfsd_mutex){+.+.}-{4:4}, at: nfsd_shutdown_threads+0x5b/0xf0 fs/nfsd/nfssvc.c:576
6 locks held by syz-executor/30261:
1 lock held by syz.2.7975/30264:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.2.7975/30265:
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f4fb420 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.5.7981/30310:
1 lock held by modprobe/30317:

=============================================

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 nmi_cpu_backtrace.cold+0x12d/0x151 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x1d7/0x230 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:161 [inline]
 __sys_info lib/sys_info.c:157 [inline]
 sys_info+0x141/0x190 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:346 [inline]
 watchdog+0xd18/0x1040 kernel/hung_task.c:515
 kthread+0x370/0x450 kernel/kthread.c:436
 ret_from_fork+0x72b/0xd50 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/15 12:01 upstream 1f5ffc672165 2b1eb0ca .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in vt_ioctl
2026/04/12 00:59 upstream e753c16cb3dd 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in vt_ioctl
* Struck through repros no longer work on HEAD.