[syzbot] [sctp?] kernel panic: corrupted stack end in sctp_setsockopt

[syzbot] [sctp?] kernel panic: corrupted stack end in sctp_setsockopt

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    71c3e5409eef Merge remote-tracking branch 'will/for-next/p..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=11a360a5580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=42bd821301b42742
dashboard link: https://syzkaller.appspot.com/bug?extid=107afda010b4507a5c80
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7596ece97a32/disk-71c3e540.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4d2c36351098/vmlinux-71c3e540.xz
kernel image: https://storage.googleapis.com/syzbot-assets/396ce0b85b3c/Image-71c3e540.gz.xz

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

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 UID: 0 PID: 10678 Comm: syz.6.1395 Tainted: G   M         L      syzkaller #0 PREEMPT 
Tainted: [M]=MACHINE_CHECK, [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/23/2026
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C)
 __dump_stack+0x30/0x40 lib/dump_stack.c:94
 dump_stack_lvl+0x30/0x12c lib/dump_stack.c:120
 dump_stack+0x1c/0x28 lib/dump_stack.c:129
 vpanic+0x594/0xaf8 kernel/panic.c:651
 vpanic+0x0/0xaf8 kernel/panic.c:788
 schedule_debug kernel/sched/core.c:6103 [inline]
 __schedule+0x18a0/0x2b00 kernel/sched/core.c:7133
 __schedule_loop kernel/sched/core.c:7361 [inline]
 schedule+0x13c/0x20c kernel/sched/core.c:7376
 __lock_sock+0x124/0x260 net/core/sock.c:3245
 lock_sock_nested+0xd4/0x110 net/core/sock.c:3858
 lock_sock include/net/sock.h:1713 [inline]
 sctp_setsockopt+0x1d4/0xe70 net/sctp/socket.c:4609
 sock_common_setsockopt+0xb0/0xcc net/core/sock.c:4050
 do_sock_setsockopt+0x1f0/0x330 net/socket.c:2397
 __sys_setsockopt+0x104/0x170 net/socket.c:2422
 __do_sys_setsockopt net/socket.c:2428 [inline]
 __se_sys_setsockopt net/socket.c:2425 [inline]
 __arm64_sys_setsockopt+0xc8/0xe4 net/socket.c:2425
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:796
 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:815
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606
Kernel Offset: disabled
CPU features: 0x0,50000000,00f00020,9c080a02,a84ff6a7
Memory Limit: none
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 syzkaller@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