syzbot


kernel panic: stack is corrupted in __schedule (4)

Status: upstream: reported syz repro on 2024/08/20 16:14
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+107a9ed6ac26198d4907@syzkaller.appspotmail.com
First crash: 333d, last: 13d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernel?] kernel panic: stack is corrupted in __schedule (4) 0 (2) 2025/02/01 14:46
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: stack is corrupted in __schedule (3) kernel 2 946d 955d 0/28 auto-obsoleted due to no activity on 2022/11/23 03:17
linux-6.1 kernel panic: stack is corrupted in __schedule 1 312d 312d 0/3 auto-obsoleted due to no activity on 2024/08/27 17:04
linux-6.1 kernel panic: stack is corrupted in __schedule (2) 4 73d 160d 0/3 upstream: reported on 2024/10/19 00:59
upstream kernel panic: stack is corrupted in __schedule kernel 1 1677d 1673d 0/28 auto-closed as invalid on 2020/11/21 13:35
upstream kernel panic: stack is corrupted in __schedule (2) kernel 1 1216d 1212d 0/28 auto-closed as invalid on 2022/01/26 17:30

Sample crash report:
loop0: detected capacity change from 0 to 4096
ntfs3(loop0): Different NTFS sector size (2048) and media sector size (512).
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x22fc/0x4c90
CPU: 0 UID: 0 PID: 7666 Comm: syz.0.1098 Not tainted 6.14.0-rc6-syzkaller-00115-ge3a854b577cb #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 panic+0x349/0x880 kernel/panic.c:354
 __stack_chk_fail+0x15/0x20 kernel/panic.c:836
 __schedule+0x22fc/0x4c90
 preempt_schedule_irq+0xfb/0x1c0 kernel/sched/core.c:7087
 irqentry_exit+0x5e/0x90 kernel/entry/common.c:354
 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702
RIP: 0010:get_current arch/x86/include/asm/current.h:49 [inline]
RIP: 0010:write_comp_data kernel/kcov.c:245 [inline]
RIP: 0010:__sanitizer_cov_trace_const_cmp4+0x8/0x90 kernel/kcov.c:314
Code: 44 0a 20 c3 cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 4c 8b 04 24 <65> 48 8b 14 25 80 d6 03 00 65 8b 05 20 f3 41 7e 25 00 01 ff 00 74
RSP: 0018:ffffc9000d2b72c0 EFLAGS: 00000246
RAX: 0000000000000001 RBX: 0000000000000001 RCX: ffff88801fb68000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81d14e84 R09: 1ffffffff28a9908
R10: dffffc0000000000 R11: fffffbfff28a9909 R12: ffff88801fb68000
R13: dffffc0000000000 R14: 0000000000000000 R15: 00007f70a3f8d169
 rcu_read_unlock include/linux/rcupdate.h:878 [inline]
 is_bpf_text_address+0x1f4/0x2a0 kernel/bpf/core.c:774
 kernel_text_address+0xa7/0xe0 kernel/extable.c:125
 __kernel_text_address+0xd/0x40 kernel/extable.c:79
 unwind_get_return_address+0x4d/0x90 arch/x86/kernel/unwind_orc.c:369
 arch_stack_walk+0xfd/0x150 arch/x86/kernel/stacktrace.c:26
 stack_trace_save+0x118/0x1d0 kernel/stacktrace.c:122
 kasan_save_stack mm/kasan/common.c:47 [inline]
 kasan_save_track+0x3f/0x80 mm/kasan/common.c:68
 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:576
 poison_slab_object mm/kasan/common.c:247 [inline]
 __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264
 kasan_slab_free include/linux/kasan.h:233 [inline]
 slab_free_hook mm/slub.c:2353 [inline]
 slab_free mm/slub.c:4609 [inline]
 kmem_cache_free+0x195/0x410 mm/slub.c:4711
 vma_lock_free kernel/fork.c:458 [inline]
 __vm_area_free+0xe3/0x110 kernel/fork.c:514
 exit_mmap+0x6b9/0xd40 mm/mmap.c:1308
 __mmput+0x115/0x420 kernel/fork.c:1356
 exit_mm+0x220/0x310 kernel/exit.c:570
 do_exit+0x9ad/0x28e0 kernel/exit.c:925
 do_group_exit+0x207/0x2c0 kernel/exit.c:1087
 get_signal+0x168c/0x1720 kernel/signal.c:3036
 arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:337
 exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
 exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
 syscall_exit_to_user_mode+0xce/0x340 kernel/entry/common.c:218
 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f70a3f8d169
Code: Unable to access opcode bytes at 0x7f70a3f8d13f.
RSP: 002b:00007f70a4ecd0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 00007f70a41a5fa8 RCX: 00007f70a3f8d169
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007f70a41a5fac
RBP: 00007f70a41a5fa0 R08: 7fffffffffffffff R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 00007f70a41a5fac
R13: 0000000000000000 R14: 00007ffc0ac27960 R15: 00007ffc0ac27a48
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
----------------
Code disassembly (best guess):
   0:	44 0a 20             	or     (%rax),%r12b
   3:	c3                   	ret
   4:	cc                   	int3
   5:	cc                   	int3
   6:	cc                   	int3
   7:	cc                   	int3
   8:	66 2e 0f 1f 84 00 00 	cs nopw 0x0(%rax,%rax,1)
   f:	00 00 00
  12:	90                   	nop
  13:	90                   	nop
  14:	90                   	nop
  15:	90                   	nop
  16:	90                   	nop
  17:	90                   	nop
  18:	90                   	nop
  19:	90                   	nop
  1a:	90                   	nop
  1b:	90                   	nop
  1c:	90                   	nop
  1d:	90                   	nop
  1e:	90                   	nop
  1f:	90                   	nop
  20:	90                   	nop
  21:	90                   	nop
  22:	f3 0f 1e fa          	endbr64
  26:	4c 8b 04 24          	mov    (%rsp),%r8
* 2a:	65 48 8b 14 25 80 d6 	mov    %gs:0x3d680,%rdx <-- trapping instruction
  31:	03 00
  33:	65 8b 05 20 f3 41 7e 	mov    %gs:0x7e41f320(%rip),%eax        # 0x7e41f35a
  3a:	25 00 01 ff 00       	and    $0xff0100,%eax
  3f:	74                   	.byte 0x74

Crashes (52):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/14 11:42 upstream e3a854b577cb e2826670 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/09 17:22 upstream 1110ce6a1e34 163f510d .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/08 21:39 upstream 8f6629c004b1 ef44b750 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/01 14:45 upstream 69e858e0b8b2 0dff8567 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/16 18:12 upstream ad1b832bf1cf 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/04/28 11:26 upstream 2c8159388952 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root kernel panic: stack is corrupted in __schedule
2025/03/14 11:40 upstream e3a854b577cb e2826670 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/14 09:44 upstream e3a854b577cb e2826670 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/12 23:51 upstream 0fed89a961ea 1a5d9317 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/12 14:09 upstream 0fed89a961ea ee70e6db .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/12 02:45 upstream 0b46b049d6ec ee70e6db .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/10 13:17 upstream 80e54e84911a 16256247 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/09 16:51 upstream 1110ce6a1e34 163f510d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/06 23:43 upstream f315296c92fd 831e3629 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/05 15:08 upstream 48a5eed9ad58 60f5d8d9 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/19 22:07 upstream 6537cfb395f3 cbd8edab .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/15 00:35 upstream 04f41cbf03ec 40a34ec9 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/08 21:12 upstream 8f6629c004b1 ef44b750 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/02 12:25 upstream 69e858e0b8b2 568559e4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/02 10:13 upstream 69e858e0b8b2 568559e4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/01 13:17 upstream 69e858e0b8b2 0dff8567 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/01/22 17:01 upstream c4b9570cfb63 25e17fd3 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/01/21 17:04 upstream 95ec54a420b8 da72ac06 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/01/09 15:02 upstream eea6e4b4dfb8 9220929f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/01/08 04:09 upstream 09a0fa92e5b4 f3558dbf .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/12/16 23:07 upstream f44d154d6e3d f93b2b55 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/12/15 08:01 upstream 2d8308bf5b67 7cbfbb3a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/12/11 23:38 upstream 231825b2e1ff 6f1b0fa8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/11/11 17:29 upstream 2d5404caa8c7 0c4b1325 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/09/28 14:21 upstream ad46e8f95e93 ba29ff75 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/09/28 14:21 upstream ad46e8f95e93 ba29ff75 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/09/27 21:31 upstream e477dba5442c 2b1784d6 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/08/28 00:06 linux-next 6f923748057a 6c853ff9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/27 20:07 linux-next 6f923748057a 6c853ff9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/23 08:02 linux-next c79c85875f1a ce8a9099 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/23 07:28 linux-next c79c85875f1a ce8a9099 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/23 01:50 linux-next 6a7917c89f21 295a4b50 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/22 23:42 linux-next 6a7917c89f21 295a4b50 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/22 16:46 linux-next 6a7917c89f21 295a4b50 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/22 02:26 linux-next eb8c5ca373cb ca02180f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/22 01:26 linux-next eb8c5ca373cb ca02180f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 20:26 linux-next eb8c5ca373cb db5852f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 19:26 linux-next eb8c5ca373cb db5852f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 17:46 linux-next eb8c5ca373cb db5852f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 08:51 linux-next eb8c5ca373cb 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 04:20 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/20 23:18 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/20 21:24 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/20 16:13 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/20 09:32 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/07/24 15:22 linux-next 9ec6ec93f2c1 b24754ac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/06/08 08:56 linux-next d35b2284e966 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
* Struck through repros no longer work on HEAD.