INFO: task hung in release_tty (5)

Status: auto-obsoleted due to no activity on 2026/11/13 16:51
Subsystems: kernel
Labels: prio:high
[Documentation on labels]
First crash: 456d, last: 95d
▶ ▼ ✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision
890debb4 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ INFO: task hung in release_tty (5) 2026/05/20 09:34 2026/05/20 09:34 2026/05/20 09:43 0909d65f
2a78e463 repro 💥 INFO: task hung in release_tty (5) 2026/03/10 12:19 2026/03/10 12:19 2026/03/10 12:19 5c03941b
▶ ▼ Similar bugs (8)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in release_tty 1 1 97d 97d 0/3 upstream: reported on 2026/08/13 23:49
upstream INFO: task hung in release_tty (2) serial 1 2 1837d 1915d 0/29 auto-closed as invalid on 2022/02/05 17:28
linux-4.19 INFO: task hung in release_tty 1 2 2312d 2384d 0/1 auto-closed as invalid on 2020/11/18 01:32
upstream INFO: task hung in release_tty (4) kernel 1 2 569d 635d 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 2317d 2516d 0/1 auto-closed as invalid on 2020/11/12 17:59
upstream INFO: task hung in release_tty (3) serial 1 3 739d 805d 0/29 auto-obsoleted due to no activity on 2025/02/07 03:06
upstream INFO: task hung in release_tty serial 1 3 2452d 2507d 0/29 auto-closed as invalid on 2020/06/30 16:07
linux-5.15 INFO: task hung in release_tty 1 1 111d 111d 0/3 auto-obsoleted due to no activity on 2026/11/07 19:14

Sample crash report:
INFO: task syz.2.849:8870 blocked for more than 143 seconds.
      Tainted: G             L      syzkaller #0
      Blocked by coredump.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.849       state:D stack:25912 pid:8870  tgid:8866  ppid:5592   task_flags:0x40054c flags:0x00080003
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5510 [inline]
 __schedule+0x125c/0x6730 kernel/sched/core.c:7234
 __schedule_loop kernel/sched/core.c:7311 [inline]
 schedule+0xdd/0x2c0 kernel/sched/core.c:7326
 schedule_timeout+0x1b2/0x280 kernel/time/sleep_timeout.c:75
 ___down_common kernel/locking/semaphore.c:293 [inline]
 __down_common+0x371/0x8b0 kernel/locking/semaphore.c:318
 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:734 [inline]
 con_shutdown+0x41/0x90 drivers/tty/vt/vt.c:3791
 release_tty+0xd7/0x5f0 drivers/tty/tty_io.c:1580
 tty_release_struct+0xb7/0xe0 drivers/tty/tty_io.c:1692
 tty_release+0xd7a/0x1300 drivers/tty/tty_io.c:1852
 __fput+0x3ff/0xb50 fs/file_table.c:512
 task_work_run+0x150/0x240 kernel/task_work.c:233
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0x951/0x2ae0 kernel/exit.c:1009
 do_group_exit+0xd5/0x2a0 kernel/exit.c:1152
 get_signal+0x1ec7/0x21e0 kernel/signal.c:3046
 arch_do_signal_or_restart+0x91/0x7e0 arch/x86/kernel/signal.c:337
 __exit_to_user_mode_loop kernel/entry/common.c:66 [inline]
 exit_to_user_mode_loop+0x139/0x6f0 kernel/entry/common.c:101
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:318 [inline]
 do_syscall_64+0x666/0x870 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f48af95e90e
RSP: 002b:00007f48b0850b28 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: 0000000000000007 RBX: 00007f48b08516c0 RCX: 00007f48af95e90e
RDX: 0000000000000002 RSI: 00007f48b0850c00 RDI: ffffffffffffff9c
RBP: 00007f48afa35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f48afc26128 R14: 00007f48afc26090 R15: 00007fff06ff81d8
 </TASK>
INFO: task syz.8.945:9247 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.8.945       state:D stack:26696 pid:9247  tgid:9243  ppid:9069   task_flags:0x400140 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5510 [inline]
 __schedule+0x125c/0x6730 kernel/sched/core.c:7234
 __schedule_loop kernel/sched/core.c:7311 [inline]
 schedule+0xdd/0x2c0 kernel/sched/core.c:7326
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7383
 __mutex_lock_common kernel/locking/mutex.c:726 [inline]
 __mutex_lock+0xccc/0x1bd0 kernel/locking/mutex.c:821
 tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
 chrdev_open+0x234/0x6a0 fs/char_dev.c:411
 do_dentry_open+0x6ab/0x14d0 fs/open.c:947
 vfs_open+0x82/0x3f0 fs/open.c:1052
 do_open fs/namei.c:4700 [inline]
 path_openat+0x2873/0x4280 fs/namei.c:4863
 do_file_open+0x20e/0x430 fs/namei.c:4892
 do_sys_openat2+0x10f/0x1e0 fs/open.c:1368
 do_sys_open fs/open.c:1374 [inline]
 __do_sys_openat fs/open.c:1390 [inline]
 __se_sys_openat fs/open.c:1385 [inline]
 __x64_sys_openat+0x12d/0x210 fs/open.c:1385
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f32b459e0d9
RSP: 002b:00007f32b540a028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f32b4825fa0 RCX: 00007f32b459e0d9
RDX: 0000000000000002 RSI: 0000200000000700 RDI: ffffffffffffff9c
RBP: 00007f32b4635024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f32b4826038 R14: 00007f32b4825fa0 R15: 00007ffcb6f21e68
 </TASK>

Showing all locks held in the system:
6 locks held by kworker/0:1/10:
 #0: ffff888023e9a540 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x12b1/0x1940 kernel/workqueue.c:3297
 #1: ffffc900000f7d08 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x988/0x1940 kernel/workqueue.c:3298
 #2: ffff88802b8551d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1104 [inline]
 #2: ffff88802b8551d8 (&dev->mutex){....}-{4:4}, at: hub_event+0x1bb/0x4420 drivers/usb/core/hub.c:5907
 #3: ffff88802d8221d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1104 [inline]
 #3: ffff88802d8221d8 (&dev->mutex){....}-{4:4}, at: __device_attach+0x7e/0x4d0 drivers/base/dd.c:1073
 #4: ffff88807dbbe1a0 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1104 [inline]
 #4: ffff88807dbbe1a0 (&dev->mutex){....}-{4:4}, at: __device_attach+0x7e/0x4d0 drivers/base/dd.c:1073
 #5: ffff888027aca080 (&ictx->lock){+.+.}-{4:4}, at: imon_init_intf0 drivers/media/rc/imon.c:2254 [inline]
 #5: ffff888027aca080 (&ictx->lock){+.+.}-{4:4}, at: imon_probe+0x93e/0x30a0 drivers/media/rc/imon.c:2453
3 locks held by kworker/u8:1/13:
1 lock held by khungtaskd/30:
 #0: ffffffff8ede8200 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8ede8200 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:840 [inline]
 #0: ffffffff8ede8200 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x3d/0x184 kernel/locking/lockdep.c:6775
2 locks held by kworker/u8:3/48:
2 locks held by kworker/0:1H/1892:
2 locks held by getty/5356:
 #0: ffff8880385180a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc900032332e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x419/0x14e0 drivers/tty/n_tty.c:2211
2 locks held by kworker/0:5/5782:
3 locks held by kworker/u8:11/6406:
6 locks held by syz.5.696/8359:
1 lock held by syz.2.849/8870:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_release_struct+0xad/0xe0 drivers/tty/tty_io.c:1691
1 lock held by syz.8.945/9247:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
4 locks held by udevd/9574:
 #0: ffff88802b2e0098 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0xe1/0x1270 fs/seq_file.c:183
 #1: ffff88807dcb0480 (&of->mutex#2){+.+.}-{4:4}, at: kernfs_seq_start+0x4f/0x2a0 fs/kernfs/file.c:165
 #2: ffff888037ec9c38 (kn->active#29){++++}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:73 [inline]
 #2: ffff888037ec9c38 (kn->active#29){++++}-{0:0}, at: kernfs_seq_start+0xbc/0x2a0 fs/kernfs/file.c:166
 #3: ffff88802d8221d8 (&dev->mutex){....}-{4:4}, at: device_lock_interruptible include/linux/device.h:1109 [inline]
 #3: ffff88802d8221d8 (&dev->mutex){....}-{4:4}, at: manufacturer_show+0x26/0xa0 drivers/usb/core/sysfs.c:142
1 lock held by syz.7.1000/9585:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.4.1085/10080:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
4 locks held by kworker/u8:12/10222:
1 lock held by syz.1.1121/10288:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.9.1130/10385:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x539/0xfa0 drivers/tty/tty_io.c:2120
1 lock held by syz.0.1173/10698:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: ptmx_open drivers/tty/pty.c:800 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0x11a/0x360 drivers/tty/pty.c:767
3 locks held by kworker/u8:17/11006:
1 lock held by syz.8.1349/11601:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: ptmx_open drivers/tty/pty.c:800 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0x11a/0x360 drivers/tty/pty.c:767
1 lock held by syz.5.1364/11639:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: ptmx_open drivers/tty/pty.c:800 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0x11a/0x360 drivers/tty/pty.c:767
1 lock held by syz.6.1367/11652:
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: ptmx_open drivers/tty/pty.c:800 [inline]
 #0: ffffffff8fb869a0 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0x11a/0x360 drivers/tty/pty.c:767

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 30 Comm: khungtaskd Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/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:122
 nmi_trigger_cpumask_backtrace+0x21c/0x2a0 lib/nmi_backtrace.c:65
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [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:353 [inline]
 watchdog+0xcb1/0x1030 kernel/hung_task.c:561
 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 (19):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/15 16:49 upstream 15ef2f78c49d 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in release_tty
2026/08/15 15:13 upstream 15ef2f78c49d 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in release_tty
2026/07/30 19:12 upstream 11028ab62899 aaffb173 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in release_tty
2026/06/08 07:02 upstream c68691dc1dca cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in release_tty
2026/04/05 22:25 upstream 1791c390149f 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in release_tty
2026/03/25 17:57 upstream bbeb83d3182a 4367a094 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in release_tty
2026/03/21 16:42 upstream a0c83177734a 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in release_tty
2026/03/05 05:42 upstream ecc64d2dc9ff a9fe5c9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in release_tty
2026/03/01 14:14 upstream eb71ab2bf722 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in release_tty
2026/02/02 18:55 upstream 18f7fcd5e69a 018ebef2 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in release_tty
2026/01/22 17:08 upstream a66191c590b3 a16aed1d .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in release_tty
2025/12/24 01:01 upstream b927546677c8 d1b870e1 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in release_tty
2025/10/13 15:09 upstream 3a8660878839 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in release_tty
2025/10/12 04:59 upstream 98906f9d850e ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in release_tty
2025/08/19 13:28 upstream be48bcf004f9 523f460e .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in release_tty
2026/05/25 13:34 upstream e7ae89a0c97c c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in release_tty
2026/05/20 01:31 upstream 27fa82620cba 0909d65f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in release_tty
2026/04/11 19:42 upstream e774d5f1bc27 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in release_tty
2026/04/07 02:02 upstream bfe62a454542 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in release_tty
* Struck through repros no longer work on HEAD.