[moderation] [kernel?] BUG: unable to handle kernel paging request in timerqueue_add

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6d69b6c12fce Merge tag 'nfs-for-6.10-1' of git://git.linux..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1297b23c980000
kernel config: https://syzkaller.appspot.com/x/.config?x=21de3d423116c304
dashboard link: https://syzkaller.appspot.com/bug?extid=cc9aa592014fa0544990
compiler: aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
CC: [anna-...@linutronix.de fred...@kernel.org linux-...@vger.kernel.org tg...@linutronix.de]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-6d69b6c1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9fa4d7c3665d/vmlinux-6d69b6c1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/131ac291917c/Image-6d69b6c1.gz.xz

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

Unable to handle kernel paging request at virtual address 007000007f8e7900
Mem abort info:
ESR = 0x0000000096000004
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
Data abort info:
ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
CM = 0, WnR = 0, TnD = 0, TagAccess = 0
GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[007000007f8e7900] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 6736 Comm: syz-executor.0 Not tainted 6.9.0-syzkaller-12124-g6d69b6c12fce #0
Hardware name: linux,dummy-virt (DT)
pstate: 814000c9 (Nzcv daIF +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
pc : rb_add_cached include/linux/rbtree.h:174 [inline]
pc : timerqueue_add+0x48/0xcc lib/timerqueue.c:40
lr : enqueue_hrtimer.constprop.0+0x44/0x60 kernel/time/hrtimer.c:1093
sp : ffff800083e43c50
x29: ffff800083e43c50 x28: fff000007f8e77c0 x27: 0000000000000040
x26: 0000000000000000 x25: ffff8000826ec840 x24: 0000000000000000
x23: fff000007f8e7780 x22: fff000007f8e7780 x21: fff000007f8e7780
x20: 0000000000000001 x19: ffff800083e43d60 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffffd5124c88
x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
x8 : ffff800083e43da0 x7 : 0000000000000000 x6 : ffff800083e43db8
x5 : 0000015ef353a300 x4 : ffff800088bebc20 x3 : ff7000007f8e78e8
x2 : ff7000007f8e78e8 x1 : fff000007f8e77e0 x0 : ffff800083e43d60
Call trace:
rb_add_cached include/linux/rbtree.h:172 [inline]
timerqueue_add+0x48/0xcc lib/timerqueue.c:40
enqueue_hrtimer.constprop.0+0x44/0x60 kernel/time/hrtimer.c:1093
__hrtimer_start_range_ns kernel/time/hrtimer.c:1260 [inline]
hrtimer_start_range_ns+0x288/0x2f8 kernel/time/hrtimer.c:1300
hrtimer_start_expires include/linux/hrtimer.h:289 [inline]
hrtimer_sleeper_start_expires kernel/time/hrtimer.c:1949 [inline]
do_nanosleep.constprop.0+0x70/0x138 kernel/time/hrtimer.c:2025
hrtimer_nanosleep+0xa4/0x114 kernel/time/hrtimer.c:2081
common_nsleep+0x44/0x6c kernel/time/posix-timers.c:1350
__do_sys_clock_nanosleep kernel/time/posix-timers.c:1396 [inline]
__se_sys_clock_nanosleep kernel/time/posix-timers.c:1373 [inline]
__arm64_sys_clock_nanosleep+0xcc/0x144 kernel/time/posix-timers.c:1373
__invoke_syscall arch/arm64/kernel/syscall.c:34 [inline]
invoke_syscall+0x48/0x118 arch/arm64/kernel/syscall.c:48
el0_svc_common.constprop.0+0x40/0xe0 arch/arm64/kernel/syscall.c:133
do_el0_svc+0x1c/0x28 arch/arm64/kernel/syscall.c:152
el0_svc+0x34/0xf8 arch/arm64/kernel/entry-common.c:712
el0t_64_sync_handler+0x100/0x12c arch/arm64/kernel/entry-common.c:730
el0t_64_sync+0x19c/0x1a0 arch/arm64/kernel/entry.S:598
Code: f9400843 91004044 b4000123 aa0303e2 (f9400c43)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: f9400843 ldr x3, [x2, #16]
4: 91004044 add x4, x2, #0x10
8: b4000123 cbz x3, 0x2c
c: aa0303e2 mov x2, x3
* 10: f9400c43 ldr x3, [x2, #24] <-- trapping instruction


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