[v6.1] kernel panic: stack is corrupted in __schedule (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 02b72ccb5f9d Linux 6.1.138
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=110a1cf4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=40498c8aeab367b8
dashboard link: https://syzkaller.appspot.com/bug?extid=7a9ee603b51c510f1a7e
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a82cf4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=150a1cf4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/741917d96f57/disk-02b72ccb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b5e0c69249ae/vmlinux-02b72ccb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/06bfb546fb37/bzImage-02b72ccb.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/ffd9d8707f87/mount_0.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/e2bd16b0f8b9/mount_3.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=14125670580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7a9ee6...@syzkaller.appspotmail.com

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+0x143d/0x40d0 kernel/sched/core.c:-1
CPU: 1 PID: 4611 Comm: syz-executor153 Not tainted 6.1.138-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
panic+0x2c9/0x710 kernel/panic.c:339
__stack_chk_fail+0x10/0x10 kernel/panic.c:767
__schedule+0x143d/0x40d0 kernel/sched/core.c:-1
preempt_schedule_irq+0xb1/0x150 kernel/sched/core.c:6873
irqentry_exit+0x63/0x70 kernel/entry/common.c:439
asm_sysvec_reschedule_ipi+0x16/0x20 arch/x86/include/asm/idtentry.h:696
RIP: 0010:preempt_count_add+0x2e/0x190 kernel/sched/core.c:5705
Code: 53 49 bf 00 00 00 00 00 fc ff df 48 c7 c0 20 f1 9b 96 48 c1 e8 03 42 0f b6 04 38 84 c0 0f 85 eb 00 00 00 83 3d 42 48 44 15 00 <75> 07 65 8b 05 61 c6 aa 7e 65 01 3d 5a c6 aa 7e 48 c7 c0 20 f1 9b
RSP: 0018:ffffc9000c237a58 EFLAGS: 00000246
RAX: 0000000000000004 RBX: ffff88806295c538 RCX: ffffffff969bf103
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: ffffc9000c237d28 R08: dffffc0000000000 R09: ffffed100c52b8d8
R10: ffffed100c52b8d8 R11: 1ffff1100c52b8d7 R12: ffff88806295c6b8
R13: 0000000000000000 R14: ffff88806295c6b8 R15: dffffc0000000000
__raw_spin_lock include/linux/spinlock_api_smp.h:132 [inline]
_raw_spin_lock+0xe/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
_atomic_dec_and_lock+0xa5/0x110 lib/dec_and_lock.c:28
iput+0x7f/0x980 fs/inode.c:1852
ntfs_fill_super+0x388a/0x3f30 fs/ntfs3/super.c:1214
get_tree_bdev+0x3f1/0x610 fs/super.c:1366
vfs_get_tree+0x88/0x270 fs/super.c:1573
do_new_mount+0x24a/0xa40 fs/namespace.c:3057
do_mount fs/namespace.c:3400 [inline]
__do_sys_mount fs/namespace.c:3608 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3585
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f57fc5a741a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 7e 09 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffedd533d68 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffedd533dc0 RCX: 00007f57fc5a741a
RDX: 000020000001f340 RSI: 0000200000000040 RDI: 00007ffedd533dc0
RBP: 0000200000000040 R08: 00007ffedd533e00 R09: 000000000001f32b
R10: 0000000000000890 R11: 0000000000000286 R12: 000020000001f340
R13: 00007ffedd533e00 R14: 000000000001f331 R15: 0000200000000000
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
----------------
Code disassembly (best guess):
0: 53 push %rbx
1: 49 bf 00 00 00 00 00 movabs $0xdffffc0000000000,%r15
8: fc ff df
b: 48 c7 c0 20 f1 9b 96 mov $0xffffffff969bf120,%rax
12: 48 c1 e8 03 shr $0x3,%rax
16: 42 0f b6 04 38 movzbl (%rax,%r15,1),%eax
1b: 84 c0 test %al,%al
1d: 0f 85 eb 00 00 00 jne 0x10e
23: 83 3d 42 48 44 15 00 cmpl $0x0,0x15444842(%rip) # 0x1544486c
* 2a: 75 07 jne 0x33 <-- trapping instruction
2c: 65 8b 05 61 c6 aa 7e mov %gs:0x7eaac661(%rip),%eax # 0x7eaac694
33: 65 01 3d 5a c6 aa 7e add %edi,%gs:0x7eaac65a(%rip) # 0x7eaac694
3a: 48 rex.W
3b: c7 .byte 0xc7
3c: c0 20 f1 shlb $0xf1,(%rax)
3f: 9b fwait


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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]

syzbot suspects this issue was fixed by commit:

commit c58c6b532b7b69537cfd9ef701c7e37cdcf79dc4
Author: Ye Bin <yeb...@huawei.com>
Date: Mon Aug 11 14:18:30 2025 +0000

fs/buffer: fix use-after-free when call bh_read() helper

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=158886e2580000
start commit: 58485ff1a74f Linux 6.1.141
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=c186557a18643a0b
dashboard link: https://syzkaller.appspot.com/bug?extid=7a9ee603b51c510f1a7e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a06f0c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1786370c580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: fs/buffer: fix use-after-free when call bh_read() helper

For information about bisection process see: https://goo.gl/tpsmEJ#bisection