INFO: task hung in __zap_vma_range

Status: auto-obsoleted due to no activity on 2026/10/02 06:25
Subsystems: mm
Labels: prio:high
[Documentation on labels]
First crash: 105d, last: 105d
▶ ▼ ✨ AI Jobs (5)
ID Workflow Result Correct Bug Created Started Finished Revision
7d522f94 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ✅ VMHostTrigger: ❌ ❓ INFO: task hung in __zap_vma_range 2026/07/23 00:00 2026/07/23 00:00 2026/07/23 00:43 44995053
1a76cf76 assessment-security 💥 INFO: task hung in __zap_vma_range 2026/07/14 00:01 2026/07/14 00:01 2026/07/14 00:19 2130f682
1552bf66 assessment-security 💥 INFO: task hung in __zap_vma_range 2026/07/10 00:01 2026/07/10 00:01 2026/07/10 00:20 6e8eff30
d46613be assessment-security 💥 INFO: task hung in __zap_vma_range 2026/07/07 00:02 2026/07/07 00:02 2026/07/07 00:17 93f57954
ef0bd73a assessment-security 💥 INFO: task hung in __zap_vma_range 2026/07/06 00:00 2026/07/06 00:00 2026/07/06 00:19 93f57954

Sample crash report:
INFO: task syz.7.455:5824 blocked for more than 430 seconds.
      Not tainted syzkaller #0
      Blocked by coredump.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.7.455       state:R  running task     stack:0     pid:5824  tgid:5823  ppid:5409   task_flags:0x40044c flags:0x00000010
Call trace:
 __switch_to+0x5e0/0xb70 arch/arm64/kernel/process.c:810 (T)
 context_switch kernel/sched/core.c:5388 [inline]
 __schedule+0x2554/0x3828 kernel/sched/core.c:7189
 preempt_schedule_common+0x118/0x210 kernel/sched/core.c:7370
 preempt_schedule+0x5c/0x70 kernel/sched/core.c:7394
 __raw_spin_unlock include/linux/spinlock_api_smp.h:169 [inline]
 _raw_spin_unlock+0x90/0x94 kernel/locking/spinlock.c:190
 spin_unlock include/linux/spinlock.h:390 [inline]
 zap_pte_range mm/memory.c:1948 [inline]
 zap_pmd_range mm/memory.c:2004 [inline]
 zap_pud_range mm/memory.c:2032 [inline]
 zap_p4d_range mm/memory.c:2053 [inline]
 __zap_vma_range+0x3574/0x484c mm/memory.c:2093
 unmap_vmas+0x21c/0x414 mm/memory.c:2162
 exit_mmap+0x170/0xb64 mm/mmap.c:1300
 __mmput+0x10c/0x51c kernel/fork.c:1178
 mmput+0x70/0xa8 kernel/fork.c:1201
 exit_mm+0x1e4/0x2f8 kernel/exit.c:582
 do_exit+0x828/0x23d8 kernel/exit.c:964
 do_group_exit+0x1d4/0x2ac kernel/exit.c:1119
 get_signal+0x13f8/0x1504 kernel/signal.c:3037
 arch_do_signal_or_restart+0x23c/0x4b50 arch/arm64/kernel/signal.c:1665
 __exit_to_user_mode_loop kernel/entry/common.c:64 [inline]
 exit_to_user_mode_loop+0x88/0x188 kernel/entry/common.c:98
 __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]
 arm64_syscall_exit_to_user_mode arch/arm64/kernel/entry-common.c:88 [inline]
 el0_svc+0x184/0x238 arch/arm64/kernel/entry-common.c:741
 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:759
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:594

Showing all locks held in the system:
1 lock held by khungtaskd/26:
 #0: ffff800087db4518 (rcu_read_lock){....}-{1:3}, at: __ll_sc_atomic64_fetch_or arch/arm64/include/asm/atomic_ll_sc.h:-1 [inline]
 #0: ffff800087db4518 (rcu_read_lock){....}-{1:3}, at: arch_atomic64_fetch_or arch/arm64/include/asm/atomic.h:86 [inline]
 #0: ffff800087db4518 (rcu_read_lock){....}-{1:3}, at: raw_atomic64_fetch_or include/linux/atomic/atomic-arch-fallback.h:3816 [inline]
 #0: ffff800087db4518 (rcu_read_lock){....}-{1:3}, at: raw_atomic_long_fetch_or include/linux/atomic/atomic-long.h:1090 [inline]
 #0: ffff800087db4518 (rcu_read_lock){....}-{1:3}, at: arch_test_and_set_bit include/asm-generic/bitops/atomic.h:42 [inline]
 #0: ffff800087db4518 (rcu_read_lock){....}-{1:3}, at: test_and_set_bit include/asm-generic/bitops/instrumented-atomic.h:72 [inline]
 #0: ffff800087db4518 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire+0x0/0x44 kernel/sched/sched.h:3869
1 lock held by klogd/3167:
2 locks held by getty/3232:
 #0: d0f000001277a0a0 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
 #1: 20ff80008cb4b2e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x314/0x1214 drivers/tty/n_tty.c:2211
2 locks held by syz-executor/3362:
3 locks held by kworker/u4:6/3421:
3 locks held by kworker/u4:2/4312:
3 locks held by kworker/u4:5/4747:
2 locks held by kworker/u4:8/4797:
 #0: 8cf000000d036540 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_one_work+0x804/0x1d5c kernel/workqueue.c:3288
 #1: ffff80008e247cb8 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x890/0x1d5c kernel/workqueue.c:3288
3 locks held by kworker/u4:3/5177:
3 locks held by kworker/u4:11/5261:
2 locks held by kworker/u4:13/5536:
 #0: 8cf000000d036540 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_one_work+0x804/0x1d5c kernel/workqueue.c:3288
 #1: ffff80008ec07cb8 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x890/0x1d5c kernel/workqueue.c:3288
3 locks held by kworker/u4:4/5719:
2 locks held by syz.6.454/5815:
2 locks held by syz.7.455/5824:
4 locks held by modprobe/6014:
1 lock held by modprobe/6015:
3 locks held by dhcpcd-run-hook/6016:

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


Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/07/04 06:19 git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git next 1ee27dacbe5d fcece630 .config console log report info ci-qemu-native-arm64-kvm INFO: task hung in __zap_vma_range
* Struck through repros no longer work on HEAD.