INFO: task hung in release_tty

Status: upstream: reported on 2026/08/13 23:49
Reported-by: syzbot+25213621a58f0d956ce8@syzkaller.appspotmail.com
First crash: 1d01h, last: 1d01h
Similar bugs (7)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in release_tty (2) serial 1 2 1741d 1819d 0/29 auto-closed as invalid on 2022/02/05 17:28
linux-4.19 INFO: task hung in release_tty 1 2 2215d 2288d 0/1 auto-closed as invalid on 2020/11/18 01:32
upstream INFO: task hung in release_tty (4) kernel 1 2 472d 539d 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 2221d 2420d 0/1 auto-closed as invalid on 2020/11/12 17:59
upstream INFO: task hung in release_tty (3) serial 1 3 643d 709d 0/29 auto-obsoleted due to no activity on 2025/02/07 03:06
upstream INFO: task hung in release_tty serial 1 3 2356d 2411d 0/29 auto-closed as invalid on 2020/06/30 16:07
linux-5.15 INFO: task hung in release_tty 1 1 15d 15d 0/3 upstream: reported on 2026/07/30 19:13

Sample crash report:
INFO: task syz.5.1123:9800 blocked for more than 144 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.5.1123      state:D stack:25520 pid:9800  ppid:6912   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5246 [inline]
 __schedule+0x107f/0x4030 kernel/sched/core.c:6563
 schedule+0xb9/0x180 kernel/sched/core.c:6639
 schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2144
 ___down_common kernel/locking/semaphore.c:229 [inline]
 __down_common+0x30c/0x740 kernel/locking/semaphore.c:250
 down+0x7c/0xd0 kernel/locking/semaphore.c:64
 console_lock+0x141/0x1c0 kernel/printk/printk.c:2629
 con_shutdown+0x44/0x80 drivers/tty/vt/vt.c:3431
 release_tty+0xc9/0x560 drivers/tty/tty_io.c:1588
 tty_release_struct+0xb4/0xd0 drivers/tty/tty_io.c:1700
 tty_release+0xbc5/0x14f0 drivers/tty/tty_io.c:1860
 __fput+0x20a/0x8b0 fs/file_table.c:320
 task_work_run+0x1d0/0x260 kernel/task_work.c:203
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
 __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
 syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f2c0cd9e0d9
RSP: 002b:00007ffc0ebd2eb8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007f2c0d027da0 RCX: 00007f2c0cd9e0d9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007f2c0d027da0 R08: 0000000000000006 R09: 0000000000000000
R10: 00007f2c0d027cb0 R11: 0000000000000246 R12: 000000000006cf8f
R13: 00007f2c0d02609c R14: 000000000006cf5c R15: 00007f2c0d026090
 </TASK>
INFO: task syz.0.1126:9847 blocked for more than 144 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.1126      state:D stack:27920 pid:9847  ppid:6712   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5246 [inline]
 __schedule+0x107f/0x4030 kernel/sched/core.c:6563
 schedule+0xb9/0x180 kernel/sched/core.c:6639
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6698
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x548/0xae0 kernel/locking/mutex.c:747
 ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
 chrdev_open+0x585/0x5f0 fs/char_dev.c:414
 do_dentry_open+0x7dd/0x10b0 fs/open.c:882
 do_open fs/namei.c:3634 [inline]
 path_openat+0x2674/0x2f10 fs/namei.c:3791
 do_filp_open+0x1ee/0x420 fs/namei.c:3818
 do_sys_openat2+0x14b/0x4f0 fs/open.c:1320
 do_sys_open fs/open.c:1336 [inline]
 __do_sys_openat fs/open.c:1352 [inline]
 __se_sys_openat fs/open.c:1347 [inline]
 __x64_sys_openat+0x135/0x160 fs/open.c:1347
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f748579e0d9
RSP: 002b:00007f7486684028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f7485a25fa0 RCX: 00007f748579e0d9
RDX: 0000000000000002 RSI: 00002000000001c0 RDI: ffffffffffffff9c
RBP: 00007f7485835024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7485a26038 R14: 00007f7485a25fa0 R15: 00007ffd0f421478
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffffffff8cb2e4f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
 #0: ffffffff8cb2ed10 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
 #0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
 #0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
 #0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6527
2 locks held by getty/4029:
 #0: ffff88803015c098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41e/0x1360 drivers/tty/n_tty.c:2198
2 locks held by kworker/u4:6/4334:
 #0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc90004107d00 ((reaper_work).work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
3 locks held by kworker/0:19/5525:
 #0: ffff88802f5c2138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc90003c97d00 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #2: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x15/0x30 net/ipv6/addrconf.c:4679
4 locks held by kworker/u4:18/8640:
 #0: ffff88801761e938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc90004f0fd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #2: ffffffff8dd4ead0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
 #3: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: ieee80211_unregister_hw+0x51/0x290 net/mac80211/main.c:1477
3 locks held by kworker/u4:19/8642:
2 locks held by kworker/u4:29/8665:
 #0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
 #1: ffffc9000505fd00 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
5 locks held by syz.6.1124/9809:
1 lock held by syz.5.1123/9800:
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_release_struct+0xaa/0xd0 drivers/tty/tty_io.c:1699
1 lock held by syz.0.1126/9847:
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.8.1185/10153:
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
2 locks held by kworker/0:3/10179:
1 lock held by syz.3.1216/10272:
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
1 lock held by syz.1.1225/10301:
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
1 lock held by syz.7.1229/10314:
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz-executor/10625:
1 lock held by syz.9.1301/10722:
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.5.1405/11233:
 #0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
8 locks held by syz-executor/12251:
1 lock held by syz.2.1661/12415:
1 lock held by rm/12418:

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 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/0x24e lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3e6/0x460 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
 watchdog+0xf0e/0xf50 kernel/hung_task.c:377
 kthread+0x29d/0x330 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>

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