BUG: unable to handle kernel NULL pointer dereference in rcu_core_si

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f57a12aa375c Merge branch 'for-next/core' into for-kernelci
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=15be8395480000
kernel config: https://syzkaller.appspot.com/x/.config?x=57844d8382c36d39
dashboard link: https://syzkaller.appspot.com/bug?extid=350812017a279cb3ceb5
compiler: Debian clang version 13.0.1-6~deb11u1, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
CC: [Henry...@arm.com ak...@linux-foundation.org big...@linutronix.de linux-...@vger.kernel.org long...@huawei.com tg...@linutronix.de ubi...@gmail.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6ed1474b01ab/disk-f57a12aa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ad0121fbeed8/vmlinux-f57a12aa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/06a26b4782db/Image-f57a12aa.gz.xz

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

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
Mem abort info:
ESR = 0x0000000086000005
EC = 0x21: IABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x05: level 1 translation fault
user pgtable: 4k pages, 48-bit VAs, pgdp=0000000122e6b000
[0000000000000000] pgd=080000012afc7003, p4d=080000012afc7003, pud=0000000000000000
Internal error: Oops: 0000000086000005 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted 6.2.0-rc6-syzkaller-17530-gf57a12aa375c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : 0x0
lr : rcu_do_batch kernel/rcu/tree.c:2246 [inline]
lr : rcu_core+0x3f4/0x9f4 kernel/rcu/tree.c:2506
sp : ffff80000f4a3cd0
x29: ffff80000f4a3d10 x28: 000000000000000a x27: ffff0000c0338008
x26: 0000000000000000 x25: ffff0000c9833df0 x24: 0000000000000001
x23: ffff80000d6455f0 x22: ffff80000c15fd10 x21: ffff0000c0338000
x20: ffff80000d51c000 x19: ffff0001feff10c0 x18: 00000000000000e7
x17: ffff80000c15e8bc x16: ffff80000dd87118 x15: ffff0000c0338000
x14: 0000000000000018 x13: 0000000000000001 x12: ffff0000c0338000
x11: ff808000095ec85c x10: 0000000000000000 x9 : f72340736d2d6d00
x8 : 0000000000000000 x7 : ffff8000081fd734 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000002
x2 : 0000000000000008 x1 : ffff80000cd3a628 x0 : ffff0000c9833df0
Call trace:
0x0
rcu_core_si+0x10/0x1c kernel/rcu/tree.c:2523
_stext+0x164/0x34c
run_ksoftirqd+0x40/0x108 kernel/softirq.c:934
smpboot_thread_fn+0x248/0x3ec kernel/smpboot.c:164
kthread+0x12c/0x158 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: ???????? ???????? ???????? ???????? (????????)
---[ end trace 0000000000000000 ]---


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

[syzbot]

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