syzbot


kernel panic: stack is corrupted in debug_object_active_state

Status: upstream: reported syz repro on 2025/08/16 03:09
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+56728135217003dc6f7d@syzkaller.appspotmail.com
First crash: 9d19h, last: 9d19h
Cause bisection: introduced by (bisect log) :
commit e305509e678b3a4af2b3cfd410f409f7cdaabb52
Author: Lin Ma <linma@zju.edu.cn>
Date: Sun May 30 13:37:43 2021 +0000

  Bluetooth: use correct lock to prevent UAF of hdev object

Crash: BUG: sleeping function called from invalid context in lock_sock_nested (log)
Repro: syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ntfs3?] kernel panic: stack is corrupted in debug_object_active_state 0 (2) 2025/08/17 06:18

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: debug_object_active_state+0x204/0x260 lib/debugobjects.c:-1
CPU: 0 UID: 0 PID: 10513 Comm: syz.0.2210 Tainted: G        W           6.17.0-rc1-syzkaller-00165-gee94b00c1a64 #0 PREEMPT_{RT,(full)} 
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x99/0x250 lib/dump_stack.c:120
 vpanic+0x281/0x750 kernel/panic.c:430
 panic+0xb9/0xc0 kernel/panic.c:566
 __stack_chk_fail+0x26/0x30 kernel/panic.c:929
 debug_object_active_state+0x204/0x260 lib/debugobjects.c:-1
 debug_rcu_head_queue kernel/rcu/rcu.h:237 [inline]
 __call_rcu_common kernel/rcu/tree.c:3108 [inline]
 call_rcu+0xc3/0x9c0 kernel/rcu/tree.c:3243
 __destroy_inode+0x2da/0x670 fs/inode.c:371
 destroy_inode fs/inode.c:394 [inline]
 evict+0x797/0x9c0 fs/inode.c:834
 ntfs_fill_super+0x38fa/0x40b0 fs/ntfs3/super.c:1514
 get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1692
 vfs_get_tree+0x8f/0x2b0 fs/super.c:1815
 do_new_mount+0x2a2/0x9e0 fs/namespace.c:3805
 do_mount fs/namespace.c:4133 [inline]
 __do_sys_mount fs/namespace.c:4344 [inline]
 __se_sys_mount+0x317/0x410 fs/namespace.c:4321
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f622eac038a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f622e12de68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f622e12def0 RCX: 00007f622eac038a
RDX: 000020000001f380 RSI: 000020000001f3c0 RDI: 00007f622e12deb0
RBP: 000020000001f380 R08: 00007f622e12def0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000020000001f3c0
R13: 00007f622e12deb0 R14: 000000000001f34c R15: 000020000001f400
 </TASK>
Kernel Offset: disabled

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/15 22:28 upstream ee94b00c1a64 1804e95e .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs kernel panic: stack is corrupted in debug_object_active_state
* Struck through repros no longer work on HEAD.