[v6.1] INFO: task hung in tls_sk_proto_close (3)
0 views
Skip to first unread message
syzbot
Apr 15, 2026, 4:35:28 AM (22 hours ago) Apr 15
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 8e8fc038cad5 Linux 6.1.168
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=170e18ce580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=dfdbcce49884d291c82d
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/57beeb41ab18/disk-8e8fc038.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d759c245a93a/vmlinux-8e8fc038.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fc000e63f4e4/bzImage-8e8fc038.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dfdbcc...@syzkaller.appspotmail.com
INFO: task syz.3.5454:22920 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.5454 state:D stack:26224 pid:22920 ppid:16421 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2144
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x2c7/0x5a0 kernel/sched/completion.c:138
__flush_work+0x952/0xae0 kernel/workqueue.c:3076
__cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3163
tls_sk_proto_close+0xc4/0x8f0 net/tls/tls_main.c:328
inet_release+0x139/0x180 net/ipv4/af_inet.c:430
__sock_release net/socket.c:654 [inline]
sock_close+0xd5/0x240 net/socket.c:1399
__fput+0x22c/0x920 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:0x7f686f39c819
RSP: 002b:00007fff207307e8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007f686f617da0 RCX: 00007f686f39c819
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007f686f617da0 R08: 0000000000000006 R09: 0000000000000000
R10: 00007f686f617cb0 R11: 0000000000000246 R12: 0000000000154bf7
R13: 00007f686f61609c R14: 000000000015496a R15: 00007fff207308f0
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2df30 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2e750 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
#0: ffffffff8cb2d5a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2d5a0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2d5a0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
3 locks held by kworker/u4:3/46:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90000b77d00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
2 locks held by getty/4034:
#0: ffff88814d213098 (&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+0x429/0x1390 drivers/tty/n_tty.c:2198
2 locks held by kworker/1:4/4309:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003ec7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
3 locks held by kworker/1:7/4335:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003f67d00 ((work_completion)(&(&sw_ctx_tx->tx_work.work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffff888079064cd8 (&ctx->tx_lock){+.+.}-{3:3}, at: tx_work_handler+0xfd/0x1f0 net/tls/tls_sw.c:2602
4 locks held by kworker/u4:17/4494:
#0: ffff888017616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc900048afd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd3af10 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: caif_exit_net+0x66/0x490 net/caif/caif_dev.c:527
3 locks held by kworker/0:4/7969:
#0: ffff88814d04bd38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc900034dfd00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xca/0x14f0 net/ipv6/addrconf.c:4131
3 locks held by kworker/1:11/8190:
#0: ffff88814d04bd38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90004d3fd00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xca/0x14f0 net/ipv6/addrconf.c:4131
1 lock held by syz.3.5454/22920:
#0: ffff888073a96e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#0: ffff888073a96e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:653 [inline]
#0: ffff888073a96e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1399
1 lock held by syz-executor/24228:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
2 locks held by syz.5.5850/24670:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3d/0x1b0 drivers/net/tun.c:3492
#1: ffffffff8cb33278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#1: ffffffff8cb33278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2ec/0x890 kernel/rcu/tree_exp.h:962
1 lock held by syz.0.5852/24700:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz.0.5852/24704:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz.0.5852/24711:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz.8.5853/24697:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: __tun_chr_ioctl+0x3fc/0x1e60 drivers/net/tun.c:3104
1 lock held by syz.8.5853/24705:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: devinet_ioctl+0x288/0x1af0 net/ipv4/devinet.c:1080
1 lock held by syz.9.5856/24726:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
=============================================
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 03/18/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+0xeee/0xf30 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>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4421 Comm: kworker/u4:12 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:__get_immv32+0x220/0x330 arch/x86/lib/insn.c:560
Code: c3 3d 48 89 d8 48 c1 e8 03 42 0f b6 04 28 84 c0 75 49 40 88 2b b8 01 00 00 00 eb 07 e8 59 5f 60 f7 31 c0 48 83 c4 08 5b 41 5c <41> 5d 41 5e 41 5f 5d c3 e8 43 5f 60 f7 eb e8 e8 3c 5f 60 f7 eb e1
RSP: 0018:ffffc90004607850 EFLAGS: 00000292
RAX: 0000000000000001 RBX: 1ffff920008c0f33 RCX: ffff88802e778000
RDX: dffffc0000000000 RSI: ffffffff8e093ca0 RDI: 0000000000000008
RBP: 1ffff920008c0f04 R08: ffff88802e778000 R09: 0000000000000003
R10: 0000000000000008 R11: 0000000000000000 R12: ffffc9000460799c
R13: dffffc0000000000 R14: ffffc900046079c8 R15: 0000000000000206
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555585664e8 CR3: 000000000c88e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
insn_get_immediate+0xc09/0x1290 arch/x86/lib/insn.c:666
insn_get_length arch/x86/lib/insn.c:707 [inline]
insn_decode+0x386/0x520 arch/x86/lib/insn.c:747
arch_jump_entry_size arch/x86/kernel/jump_label.c:24 [inline]
__jump_label_patch+0x103/0x490 arch/x86/kernel/jump_label.c:45
arch_jump_label_transform_queue+0x48/0xd0 arch/x86/kernel/jump_label.c:137
__jump_label_update+0x17d/0x390 kernel/jump_label.c:510
static_key_disable_cpuslocked+0xc1/0x1a0 kernel/jump_label.c:237
static_key_disable+0x16/0x20 kernel/jump_label.c:245
toggle_allocation_gate+0x3d1/0x470 mm/kfence/core.c:835
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: 8e8fc038cad5 Linux 6.1.168
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=170e18ce580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=dfdbcce49884d291c82d
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/57beeb41ab18/disk-8e8fc038.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d759c245a93a/vmlinux-8e8fc038.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fc000e63f4e4/bzImage-8e8fc038.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+dfdbcc...@syzkaller.appspotmail.com
INFO: task syz.3.5454:22920 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.5454 state:D stack:26224 pid:22920 ppid:16421 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2144
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x2c7/0x5a0 kernel/sched/completion.c:138
__flush_work+0x952/0xae0 kernel/workqueue.c:3076
__cancel_work_timer+0x3f4/0x560 kernel/workqueue.c:3163
tls_sk_proto_close+0xc4/0x8f0 net/tls/tls_main.c:328
inet_release+0x139/0x180 net/ipv4/af_inet.c:430
__sock_release net/socket.c:654 [inline]
sock_close+0xd5/0x240 net/socket.c:1399
__fput+0x22c/0x920 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:0x7f686f39c819
RSP: 002b:00007fff207307e8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007f686f617da0 RCX: 00007f686f39c819
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00007f686f617da0 R08: 0000000000000006 R09: 0000000000000000
R10: 00007f686f617cb0 R11: 0000000000000246 R12: 0000000000154bf7
R13: 00007f686f61609c R14: 000000000015496a R15: 00007fff207308f0
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2df30 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2e750 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
#0: ffffffff8cb2d5a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2d5a0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2d5a0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
3 locks held by kworker/u4:3/46:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90000b77d00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
2 locks held by getty/4034:
#0: ffff88814d213098 (&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+0x429/0x1390 drivers/tty/n_tty.c:2198
2 locks held by kworker/1:4/4309:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003ec7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
3 locks held by kworker/1:7/4335:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003f67d00 ((work_completion)(&(&sw_ctx_tx->tx_work.work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffff888079064cd8 (&ctx->tx_lock){+.+.}-{3:3}, at: tx_work_handler+0xfd/0x1f0 net/tls/tls_sw.c:2602
4 locks held by kworker/u4:17/4494:
#0: ffff888017616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc900048afd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd3af10 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: caif_exit_net+0x66/0x490 net/caif/caif_dev.c:527
3 locks held by kworker/0:4/7969:
#0: ffff88814d04bd38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc900034dfd00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xca/0x14f0 net/ipv6/addrconf.c:4131
3 locks held by kworker/1:11/8190:
#0: ffff88814d04bd38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90004d3fd00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xca/0x14f0 net/ipv6/addrconf.c:4131
1 lock held by syz.3.5454/22920:
#0: ffff888073a96e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#0: ffff888073a96e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:653 [inline]
#0: ffff888073a96e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1399
1 lock held by syz-executor/24228:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
2 locks held by syz.5.5850/24670:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3d/0x1b0 drivers/net/tun.c:3492
#1: ffffffff8cb33278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#1: ffffffff8cb33278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2ec/0x890 kernel/rcu/tree_exp.h:962
1 lock held by syz.0.5852/24700:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz.0.5852/24704:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz.0.5852/24711:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz.8.5853/24697:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: __tun_chr_ioctl+0x3fc/0x1e60 drivers/net/tun.c:3104
1 lock held by syz.8.5853/24705:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: devinet_ioctl+0x288/0x1af0 net/ipv4/devinet.c:1080
1 lock held by syz.9.5856/24726:
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd47de8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
=============================================
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 03/18/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+0xeee/0xf30 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>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4421 Comm: kworker/u4:12 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:__get_immv32+0x220/0x330 arch/x86/lib/insn.c:560
Code: c3 3d 48 89 d8 48 c1 e8 03 42 0f b6 04 28 84 c0 75 49 40 88 2b b8 01 00 00 00 eb 07 e8 59 5f 60 f7 31 c0 48 83 c4 08 5b 41 5c <41> 5d 41 5e 41 5f 5d c3 e8 43 5f 60 f7 eb e8 e8 3c 5f 60 f7 eb e1
RSP: 0018:ffffc90004607850 EFLAGS: 00000292
RAX: 0000000000000001 RBX: 1ffff920008c0f33 RCX: ffff88802e778000
RDX: dffffc0000000000 RSI: ffffffff8e093ca0 RDI: 0000000000000008
RBP: 1ffff920008c0f04 R08: ffff88802e778000 R09: 0000000000000003
R10: 0000000000000008 R11: 0000000000000000 R12: ffffc9000460799c
R13: dffffc0000000000 R14: ffffc900046079c8 R15: 0000000000000206
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555585664e8 CR3: 000000000c88e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
insn_get_immediate+0xc09/0x1290 arch/x86/lib/insn.c:666
insn_get_length arch/x86/lib/insn.c:707 [inline]
insn_decode+0x386/0x520 arch/x86/lib/insn.c:747
arch_jump_entry_size arch/x86/kernel/jump_label.c:24 [inline]
__jump_label_patch+0x103/0x490 arch/x86/kernel/jump_label.c:45
arch_jump_label_transform_queue+0x48/0xd0 arch/x86/kernel/jump_label.c:137
__jump_label_update+0x17d/0x390 kernel/jump_label.c:510
static_key_disable_cpuslocked+0xc1/0x1a0 kernel/jump_label.c:237
static_key_disable+0x16/0x20 kernel/jump_label.c:245
toggle_allocation_gate+0x3d1/0x470 mm/kfence/core.c:835
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages