syzbot


INFO: task hung in vcs_open (10)

Status: upstream: reported on 2026/05/29 18:45
Subsystems: kernel
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+99897fb26901360e1e8e@syzkaller.appspotmail.com
First crash: 332d, last: 3d23h
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision Error
8c12c39a-2501-482f-b6f0-fb29111a40e2 assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ INFO: task hung in vcs_open (10) 2026/05/21 09:22 2026/05/21 09:22 2026/05/21 10:29 cf874a1cf36318c06202027159ddac14acf00db7

			
		
2d4c1ab4-61ae-4185-8083-af9f10881981 repro INFO: task hung in vcs_open (10) 2026/03/10 13:35 2026/03/10 17:54 2026/03/10 18:19 86914af9098a80da53c3c5d46be980c572ee29f8

			
		
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernel?] INFO: task hung in vcs_open (10) 0 (1) 2026/05/29 18:45
Similar bugs (12)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in vcs_open (5) serial 1 2 1227d 1231d 0/29 auto-obsoleted due to no activity on 2023/06/04 04:45
upstream INFO: task hung in vcs_open (9) kernel 1 11 428d 594d 0/29 auto-obsoleted due to no activity on 2025/08/10 23:55
upstream INFO: task hung in vcs_open (3) serial 1 1 1969d 1969d 0/29 auto-closed as invalid on 2021/05/22 19:06
upstream INFO: task hung in vcs_open serial 1 32 2140d 2273d 0/29 closed as dup on 2020/08/05 10:53
upstream INFO: task hung in vcs_open (2) serial 1 1 2119d 2119d 0/29 auto-closed as invalid on 2020/12/23 12:34
upstream INFO: task hung in vcs_open (7) serial 1 1 849d 849d 0/29 auto-obsoleted due to no activity on 2024/06/15 13:53
linux-4.19 INFO: task hung in vcs_open 1 11 2076d 2388d 0/1 auto-closed as invalid on 2021/03/07 01:31
upstream INFO: task hung in vcs_open (4) serial 1 2 1380d 1443d 0/29 auto-obsoleted due to no activity on 2023/01/02 16:56
linux-4.14 INFO: task hung in vcs_open 1 3 2234d 2317d 0/1 auto-closed as invalid on 2020/09/30 10:12
upstream INFO: task hung in vcs_open (6) serial 1 2 1000d 1064d 0/29 auto-obsoleted due to no activity on 2024/01/17 08:03
linux-4.19 INFO: task hung in vcs_open (2) 1 1 1359d 1359d 0/1 auto-obsoleted due to no activity on 2023/02/22 05:12
upstream INFO: task hung in vcs_open (8) nilfs serial 1 C inconclusive 7 650d 656d 28/29 fixed on 2024/11/12 23:31

Sample crash report:
INFO: task syz.5.4889:23957 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.5.4889      state:D stack:27928 pid:23957 tgid:23956 ppid:23495  task_flags:0x400040 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5510 [inline]
 __schedule+0x17d9/0x56c0 kernel/sched/core.c:7234
 __schedule_loop kernel/sched/core.c:7311 [inline]
 schedule+0x164/0x2b0 kernel/sched/core.c:7326
 schedule_timeout+0xc0/0x2c0 kernel/time/sleep_timeout.c:75
 ___down_common kernel/locking/semaphore.c:293 [inline]
 __down_common+0x3b7/0x850 kernel/locking/semaphore.c:318
 down+0x80/0xd0 kernel/locking/semaphore.c:100
 console_lock+0x58/0x90 kernel/printk/printk.c:2896
 class_console_lock_constructor include/linux/console.h:734 [inline]
 vcs_open+0x61/0xd0 drivers/tty/vt/vc_screen.c:746
 chrdev_open+0x4d9/0x600 fs/char_dev.c:411
 do_dentry_open+0x816/0x1380 fs/open.c:947
 vfs_open+0x3b/0x340 fs/open.c:1052
 do_open fs/namei.c:4700 [inline]
 path_openat+0x2e44/0x3830 fs/namei.c:4863
 do_file_open+0x23e/0x4a0 fs/namei.c:4892
 do_sys_openat2+0x115/0x200 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+0x138/0x170 fs/open.c:1385
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa8b0d9de59
RSP: 002b:00007fa8b1c10028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fa8b1025fa0 RCX: 00007fa8b0d9de59
RDX: 0000000000000000 RSI: 0000200000002fc0 RDI: ffffffffffffff9c
RBP: 00007fa8b0e33e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa8b1026038 R14: 00007fa8b1025fa0 R15: 00007fa8b114fa48
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/30:
 #0: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
 #0: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:840 [inline]
 #0: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
2 locks held by getty/5386:
 #0: ffff88803686e0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900032332e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x45a/0x1360 drivers/tty/n_tty.c:2211
6 locks held by kworker/0:3/5632:
 #0: ffff8880206c9d40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff8880206c9d40 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #1: ffffc90003acfc40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffffc90003acfc40 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #2: ffff8880237f01d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #2: ffff8880237f01d8 (&dev->mutex){....}-{4:4}, at: hub_event+0x184/0x4d30 drivers/usb/core/hub.c:5899
 #3: ffff88820425c1d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #3: ffff88820425c1d8 (&dev->mutex){....}-{4:4}, at: __device_attach+0x88/0x450 drivers/base/dd.c:1073
 #4: ffff88807258c1a0 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1102 [inline]
 #4: ffff88807258c1a0 (&dev->mutex){....}-{4:4}, at: __device_attach+0x88/0x450 drivers/base/dd.c:1073
 #5: ffff88802a863460 (hcd->bandwidth_mutex){+.+.}-{4:4}, at: usb_set_interface+0x353/0x1470 drivers/usb/core/message.c:1624
3 locks held by kworker/1:8/5761:
3 locks held by kworker/u8:4/17415:
3 locks held by kworker/1:7/17723:
 #0: ffff88801b02b140 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff88801b02b140 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #1: ffffc9000444fc40 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffffc9000444fc40 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #2: ffff888056797250 (&data->fib_lock){+.+.}-{4:4}, at: nsim_fib_event_work+0x1fd/0x3b0 drivers/net/netdevsim/fib.c:1490
3 locks held by kworker/u8:52/19970:
 #0: ffff88803184e140 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #0: ffff88803184e140 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #1: ffffc90004ddfc40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline]
 #1: ffffc90004ddfc40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405
 #2: ffffffff9002c100 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff9002c100 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_dad_work+0x116/0x15c0 net/ipv6/addrconf.c:4229
2 locks held by kworker/u8:58/19976:
6 locks held by syz.8.4647/22805:
2 locks held by syz.2.4952/24218:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
 #1: ffff88807c51c1b0 (&tty->legacy_mutex){+.+.}-{4:4}, at: tty_init_dev+0x74/0x4d0 drivers/tty/tty_io.c:1406
1 lock held by syz.7.4958/24250:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0xdc/0x2e0 drivers/tty/pty.c:800
1 lock held by syz.6.4960/24256:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.9.4964/24297:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.1.4975/24335:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.3.4977/24431:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.5.4996/24479:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.5.4996/24480:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.5.4996/24481:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0xdc/0x2e0 drivers/tty/pty.c:800
1 lock held by syz.5.4996/24483:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0xdc/0x2e0 drivers/tty/pty.c:800
1 lock held by syz.4.4991/24501:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.4.4991/24502:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.4.4991/24504:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0xdc/0x2e0 drivers/tty/pty.c:800
1 lock held by syz.4.4991/24505:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0xdc/0x2e0 drivers/tty/pty.c:800
1 lock held by syz.0.5012/24556:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.0.5012/24557:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.0.5012/24561:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0xdc/0x2e0 drivers/tty/pty.c:800
1 lock held by syz.0.5012/24562:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: ptmx_open+0xdc/0x2e0 drivers/tty/pty.c:800
1 lock held by syz.8.5028/24637:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.2.5030/24656:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.2.5030/24657:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.9.5025/24700:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.7.5034/24709:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.6.5050/24789:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz-executor/24824:
1 lock held by syz.1.5062/24853:
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open_by_driver drivers/tty/tty_io.c:2037 [inline]
 #0: ffffffff8f457b00 (tty_mutex){+.+.}-{4:4}, at: tty_open+0x204/0xcc0 drivers/tty/tty_io.c:2120
1 lock held by syz.5.5069/24887:
 #0: ffff88806feb40a0 (&kvm->slots_lock){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffff88806feb40a0 (&kvm->slots_lock){+.+.}-{4:4}, at: kvm_vm_ioctl_set_memory_region+0x64/0xa0 virt/kvm/kvm_main.c:2146

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

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 05/09/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:122
 nmi_trigger_cpumask_backtrace+0x17a/0x380 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+0x135/0x170 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:353 [inline]
 watchdog+0xfd7/0x1030 kernel/hung_task.c:561
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 17415 Comm: kworker/u8:4 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
Workqueue: events_unbound cfg80211_wiphy_work
RIP: 0010:ieee80211_get_channel_khz+0x66/0x8a0 net/wireless/util.c:-1
Code: e8 2f 7a 1d f7 48 b9 00 00 00 00 00 fc ff df 4d 8b 3f 4d 85 ff 0f 84 f1 00 00 00 4d 8d 67 14 4c 89 e0 48 c1 e8 03 0f b6 04 08 <84> c0 0f 85 7c 07 00 00 45 8b 24 24 31 ff 44 89 e6 e8 84 f1 af f6
RSP: 0018:ffffc9000354f6e8 EFLAGS: 00000a07
RAX: 0000000000000000 RBX: 000000000024cde0 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 000000000024cde0 RDI: ffff8880529b0740
RBP: ffffc9000354fa20 R08: 0000000000000078 R09: 00000000000000f2
R10: dffffc0000000000 R11: fffff520006a9e94 R12: ffff8880529b325c
R13: 1ffff920006a9f00 R14: ffff8880529b0740 R15: ffff8880529b3248
FS:  0000000000000000(0000) GS:ffff888125058000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b33b0fff8 CR3: 000000007fd44000 CR4: 00000000003526f0
DR0: 0000000000000008 DR1: 0000000000000002 DR2: 0000000000000404
DR3: ffffffffefffff14 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ieee80211_get_channel include/net/cfg80211.h:7471 [inline]
 ieee80211_rx_bss_info net/mac80211/ibss.c:1058 [inline]
 ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1545 [inline]
 ieee80211_ibss_rx_queued_mgmt+0x5d8/0x2be0 net/mac80211/ibss.c:1572
 ieee80211_iface_process_skb net/mac80211/iface.c:1763 [inline]
 ieee80211_iface_work+0x78a/0x1010 net/mac80211/iface.c:1817
 cfg80211_wiphy_work+0x29e/0x420 net/wireless/core.c:538
 process_one_work kernel/workqueue.c:3322 [inline]
 process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3405
 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3486
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (38):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/07/11 11:07 upstream d96fcfe1b7f9 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/06/19 11:42 upstream 8c13415c8a43 d7ffd47b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vcs_open
2026/06/16 23:03 upstream 6b5a2b7d9bc1 0e4b3e40 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/06/16 14:19 upstream 481329ec5b31 50bb0618 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/05/25 18:22 upstream e7ae89a0c97c c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in vcs_open
2026/05/22 02:54 upstream 6779b50faa56 e195359d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/04/26 15:29 upstream 897d54018cc9 9c2d0995 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/04/19 08:54 upstream eb5249b12507 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/03/30 15:15 upstream 7aaa8047eafd 458630d8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/03/24 05:29 upstream c369299895a5 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vcs_open
2026/03/16 16:33 upstream f338e7738378 64e21424 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/03/14 17:30 upstream 1c9982b49613 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/03/11 01:15 upstream b4f0dd314b39 4683d576 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/03/10 21:30 upstream 1f318b96cc84 4683d576 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vcs_open
2026/03/09 22:54 upstream 1f318b96cc84 176bead5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/02/07 14:13 upstream 2687c848e578 f20fc9f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2026/01/16 14:10 upstream 983d014aafb1 d1b870e1 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in vcs_open
2026/01/14 19:48 upstream c537e12daeec d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in vcs_open
2026/01/03 02:21 upstream 9b0436804460 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2025/12/20 16:03 upstream dd9b004b7ff3 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in vcs_open
2025/11/13 07:52 upstream e927c520e1ba 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in vcs_open
2025/09/30 19:08 upstream 30d4efb2f5a5 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in vcs_open
2025/09/27 11:21 upstream fec734e8d564 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in vcs_open
2025/08/22 16:08 upstream 3957a5720157 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vcs_open
2025/08/21 03:47 upstream 41cd3fd15263 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vcs_open
2025/08/20 13:17 upstream b19a97d57c15 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vcs_open
2025/08/17 11:40 upstream 99bade344cfa 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vcs_open
2025/08/17 07:34 upstream 90d970cade8e 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vcs_open
2026/07/10 15:13 upstream a635d6748234 99e64375 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
2026/07/05 21:02 upstream f105f3631d51 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
2026/06/29 05:59 upstream dc59e4fea9d8 fb92f11c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
2026/06/18 09:08 upstream e771677c937d b62b3ded .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
2026/04/29 16:58 upstream 57b8e2d666a3 804ea88f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
2026/04/22 02:43 upstream 4ee64205ffaa 0b6ab7ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
2026/04/13 01:47 upstream f5459048c38a 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
2026/03/30 09:41 upstream ac354b5cb04d 356bdfc9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
2025/12/29 06:06 upstream c875a6c32467 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
2025/12/10 23:24 upstream 0048fbb4011e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in vcs_open
* Struck through repros no longer work on HEAD.