INFO: task hung in release_tty

Status: upstream: reported on 2026/07/30 19:13
Reported-by: syzbot+d79cd68594b3cf83f1fd@syzkaller.appspotmail.com
First crash: 11d, last: 11d
Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in release_tty (2) serial 1 2 1738d 1815d 0/29 auto-closed as invalid on 2022/02/05 17:28
linux-4.19 INFO: task hung in release_tty 1 2 2212d 2285d 0/1 auto-closed as invalid on 2020/11/18 01:32
upstream INFO: task hung in release_tty (4) kernel 1 2 469d 536d 0/29 auto-obsoleted due to no activity on 2025/07/28 01:59
linux-4.14 INFO: task hung in release_tty 1 6 2218d 2416d 0/1 auto-closed as invalid on 2020/11/12 17:59
upstream INFO: task hung in release_tty (3) serial 1 3 640d 706d 0/29 auto-obsoleted due to no activity on 2025/02/07 03:06
upstream INFO: task hung in release_tty serial 1 3 2353d 2408d 0/29 auto-closed as invalid on 2020/06/30 16:07

Sample crash report:
INFO: task syz.5.1292:7691 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.5.1292      state:D stack:24880 pid: 7691 ppid:  6861 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5049 [inline]
 __schedule+0x11c3/0x4350 kernel/sched/core.c:6395
 schedule+0x11b/0x1e0 kernel/sched/core.c:6478
 schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2093
 __down_common+0x289/0x3b0 kernel/locking/semaphore.c:228
 down+0x7e/0xd0 kernel/locking/semaphore.c:63
 console_lock+0x29/0x70 kernel/printk/printk.c:2557
 con_shutdown+0x44/0x80 drivers/tty/vt/vt.c:3431
 release_tty+0xc9/0x560 drivers/tty/tty_io.c:1607
 tty_release_struct+0xb4/0xd0 drivers/tty/tty_io.c:1719
 tty_release+0xc29/0x1630 drivers/tty/tty_io.c:1880
 __fput+0x212/0x8c0 fs/file_table.c:311
 task_work_run+0x125/0x1a0 kernel/task_work.c:188
 exit_task_work include/linux/task_work.h:33 [inline]
 do_exit+0x635/0x2110 kernel/exit.c:890
 do_group_exit+0x12c/0x2f0 kernel/exit.c:1004
 get_signal+0x7eb/0x12e0 kernel/signal.c:2909
 arch_do_signal_or_restart+0xe6/0x12a0 arch/x86/kernel/signal.c:867
 handle_signal_work kernel/entry/common.c:154 [inline]
 exit_to_user_mode_loop+0x9e/0x130 kernel/entry/common.c:178
 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
 syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fc1bf10084e
RSP: 002b:00007fc1bd397b28 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: 0000000000000004 RBX: 00007fc1bd3986c0 RCX: 00007fc1bf10084e
RDX: 0000000000000002 RSI: 00007fc1bd397c00 RDI: ffffffffffffff9c
RBP: 00007fc1bf1d700c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc1bf3c8038 R14: 00007fc1bf3c7fa0 R15: 00007ffc7b849cc8
 </TASK>

Showing all locks held in the system:
4 locks held by kworker/u4:0/9:
1 lock held by khungtaskd/27:
 #0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
5 locks held by kworker/u4:3/155:
 #0: ffff888016dcd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc90001fd7d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffffffff8d441550 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:589
 #3: ffff8880304113e8 (&wg->device_update_lock){+.+.}-{3:3}, at: wg_destruct+0x112/0x300 drivers/net/wireguard/device.c:233
 #4: ffffffff8c3239e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
 #4: ffffffff8c3239e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2d1/0x750 kernel/rcu/tree_exp.h:845
2 locks held by getty/3944:
 #0: ffff88802c3bd098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002d032e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x594/0x1a50 drivers/tty/n_tty.c:2158
2 locks held by kworker/u4:6/4243:
 #0: ffff888016c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc90003d8fd00 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
5 locks held by syz.3.1046/6814:
1 lock held by syz.5.1292/7691:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_release_struct+0xaa/0xd0 drivers/tty/tty_io.c:1718
3 locks held by kworker/0:16/7769:
 #0: ffff88802af8b538 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000358fd00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffffffff8d44d488 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x1530 net/ipv6/addrconf.c:4120
3 locks held by kworker/0:19/7772:
3 locks held by kworker/0:22/7775:
 #0: ffff8881417e7538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000362fd00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffff888023de9220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:809 [inline]
 #2: ffff888023de9220 (&dev->mutex){....}-{3:3}, at: hub_event+0x178/0x5260 drivers/usb/core/hub.c:5827
2 locks held by kworker/0:23/8918:
 #0: ffff888016c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc900031dfd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
1 lock held by syz.9.1609/8989:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
2 locks held by syz.0.1712/9378:
 #0: ffff88807c521270 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2bf/0x370 fs/file.c:1056
 #1: ffff88802234bc30 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0x9d/0xc50 fs/seq_file.c:182
1 lock held by syz.0.1712/9379:
 #0: ffff88802234bc30 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0x9d/0xc50 fs/seq_file.c:182
1 lock held by syz.0.1712/9380:
 #0: ffff88807c521270 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2bf/0x370 fs/file.c:1056
1 lock held by syz.7.1747/9515:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.3.1760/9609:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.2.1786/9717:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.5.1815/10015:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.9.1978/10705:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.8.2015/10835:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
3 locks held by syz.6.2019/10852:
 #0: ffff888077902af0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2bf/0x370 fs/file.c:1056
 #1: ffff8880795d41c8 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0x9d/0xc50 fs/seq_file.c:182
 #2: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: t_start+0x17/0x50 fs/proc/proc_tty.c:108
1 lock held by syz.1.2036/10908:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.0.2057/11005:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz-executor/11481:
1 lock held by syz.4.2094/11516:
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
 #0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.2.2106/11582:
 #0: ffff888042b7dc28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
 #0: ffff888042b7dc28 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x16c/0x2d0 mm/util.c:549
2 locks held by syz.2.2106/11583:
1 lock held by modprobe/11594:
1 lock held by rm/11595:

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
 watchdog+0xe1b/0xe60 kernel/hung_task.c:369
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/07/30 19:13 linux-5.15.y 6e2fd6534337 aaffb173 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_tty
* Struck through repros no longer work on HEAD.