[moderation] [integrity?] [lsm?] kernel panic: stack is corrupted in arch_stack_walk

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f07044dd0df0 Merge tag 'nfsd-6.13-1' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=100c2adf980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d269ef41b9262400
dashboard link: https://syzkaller.appspot.com/bug?extid=5b7f4dca2b9fbba926ad
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [dmitry....@gmail.com eric.s...@oracle.com jmo...@namei.org linux-i...@vger.kernel.org linux-...@vger.kernel.org linux-secu...@vger.kernel.org pa...@paul-moore.com robert...@huawei.com se...@hallyn.com zo...@linux.ibm.com]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-f07044dd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c96129e7b4bc/vmlinux-f07044dd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f4bcd98eacc8/bzImage-f07044dd.xz

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

loop0: detected capacity change from 0 to 4096
=======================================================
WARNING: The mand mount option has been deprecated and
and is ignored by this kernel. Remove the mand
option from the mount to silence this warning.
=======================================================
ntfs3(loop0): Different NTFS sector size (2048) and media sector size (512).
process 'syz.0.0' launched './file1' with NULL argv: empty string added
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: arch_stack_walk+0x14c/0x150
CPU: 0 UID: 0 PID: 5315 Comm: syz.0.0 Not tainted 6.13.0-rc4-syzkaller-00004-gf07044dd0df0 #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
arch_stack_walk+0x14c/0x150
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
poison_kmalloc_redzone mm/kasan/common.c:377 [inline]
__kasan_kmalloc+0x98/0xb0 mm/kasan/common.c:394
kasan_kmalloc include/linux/kasan.h:260 [inline]
__do_kmalloc_node mm/slub.c:4298 [inline]
__kmalloc_noprof+0x285/0x4c0 mm/slub.c:4310
kmalloc_noprof include/linux/slab.h:905 [inline]
kzalloc_noprof include/linux/slab.h:1037 [inline]
ima_alloc_init_template+0x8b/0x6e0 security/integrity/ima/ima_api.c:50
ima_store_measurement+0x289/0x6f0 security/integrity/ima/ima_api.c:376
process_measurement+0x150b/0x1fb0 security/integrity/ima/ima_main.c:380
ima_bprm_check+0xfd/0x200 security/integrity/ima/ima_main.c:547
security_bprm_check+0xd2/0x250 security/security.c:1296
search_binary_handler fs/exec.c:1736 [inline]
exec_binprm fs/exec.c:1790 [inline]
bprm_execve+0xa53/0x17a0 fs/exec.c:1842
do_execveat_common+0x55f/0x6f0 fs/exec.c:1949
do_execveat fs/exec.c:2034 [inline]
__do_sys_execveat fs/exec.c:2108 [inline]
__se_sys_execveat fs/exec.c:2102 [inline]
__x64_sys_execveat+0xc4/0xe0 fs/exec.c:2102
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f98c8385d29
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007f98c919a038 EFLAGS: 00000246 ORIG_RAX: 0000000000000142
RAX: ffffffffffffffda RBX: 00007f98c8575fa0 RCX: 00007f98c8385d29
RDX: 0000000000000000 RSI: 0000000020000480 RDI: ffffffffffffff9c
RBP: 00007f98c8401aa8 R08: 0000000000001000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f98c8575fa0 R15: 00007ffd5988a158
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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 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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.