INFO: task hung in ptmx_open

Status: upstream: reported on 2026/08/15 23:38
Reported-by: syzbot+eb27b8b4b43a076e4af9@syzkaller.appspotmail.com
First crash: 9h03m, last: 9h03m
Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in ptmx_open 1 5 4d05h 18d 0/3 upstream: reported on 2026/07/29 05:43
upstream INFO: task hung in ptmx_open serial 1 4 1654d 1729d 0/29 closed as invalid on 2022/02/08 09:40
linux-6.1 INFO: task hung in ptmx_open 1 1 16d 16d 0/3 upstream: reported on 2026/07/30 13:51
android-49 INFO: task hung in ptmx_open 1 1 2885d 2885d 0/3 auto-closed as invalid on 2019/03/21 04:01
upstream INFO: task hung in ptmx_open (2) serial 1 6 474d 639d 0/29 auto-obsoleted due to no activity on 2025/07/27 16:38
upstream INFO: task hung in ptmx_open (3) prio:high serial 1 7 116d 326d 0/29 auto-obsoleted due to no activity on 2026/07/20 22:39

Sample crash report:
INFO: task syz.0.3543:18213 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.3543      state:D stack:27912 pid:18213 ppid:15197  flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5382 [inline]
 __schedule+0x15ae/0x4660 kernel/sched/core.c:6701
 schedule+0xbd/0x170 kernel/sched/core.c:6775
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6834
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x673/0xc80 kernel/locking/mutex.c:747
 ptmx_open+0xd0/0x2c0 drivers/tty/pty.c:823
 chrdev_open+0x58c/0x600 fs/char_dev.c:414
 do_dentry_open+0x880/0x14b0 fs/open.c:929
 do_open fs/namei.c:3683 [inline]
 path_openat+0x284f/0x3270 fs/namei.c:3844
 do_filp_open+0x1f2/0x430 fs/namei.c:3871
 do_sys_openat2+0x134/0x1d0 fs/open.c:1422
 do_sys_open fs/open.c:1437 [inline]
 __do_sys_openat fs/open.c:1453 [inline]
 __se_sys_openat fs/open.c:1448 [inline]
 __x64_sys_openat+0x139/0x160 fs/open.c:1448
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7faf5679e0d9
RSP: 002b:00007faf57641028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007faf56a25fa0 RCX: 00007faf5679e0d9
RDX: 0000000000101000 RSI: 0000200000000000 RDI: ffffffffffffff9c
RBP: 00007faf56835024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007faf56a26038 R14: 00007faf56a25fa0 R15: 00007ffe591db338
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
 #0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
 #0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by getty/5532:
 #0: ffff88802d4350a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x428/0x1370 drivers/tty/n_tty.c:2217
4 locks held by syz.7.3541/18202:
1 lock held by syz.0.3543/18213:
 #0: ffffffff8d8b6de8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd0/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.9.3561/18378:
 #0: ffffffff8d8b6de8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
 #0: ffffffff8d8b6de8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.3.3595/18533:
 #0: ffffffff8d8b6de8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
 #0: ffffffff8d8b6de8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.2.3873/19540:
 #0: ffffffff8d8b6de8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
 #0: ffffffff8d8b6de8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
1 lock held by syz.8.3928/19807:
 #0: ffffffff8d8b6de8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2044 [inline]
 #0: ffffffff8d8b6de8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x211/0xcc0 drivers/tty/tty_io.c:2127
2 locks held by syz.6.3954/19932:
3 locks held by dhcpcd-run-hook/19943:

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

NMI backtrace for cpu 0
CPU: 0 PID: 29 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+0x18c/0x250 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3a6/0x3e0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xf59/0xfa0 kernel/hung_task.c:379
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>

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