[moderation] [net?] BUG: unable to handle kernel NULL pointer dereference in pc_clock_gettime

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: bf45a62baffc 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=158b6304580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd2356106f507975
dashboard link: https://syzkaller.appspot.com/bug?extid=20c39988b29c15d4db83
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
CC: [andrew...@lunn.ch da...@davemloft.net edum...@google.com ku...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org pab...@redhat.com richard...@gmail.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f0d4874557e9/disk-bf45a62b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0bf44a13b5b2/vmlinux-bf45a62b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/18db8bc9907c/Image-bf45a62b.gz.xz

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

loop0: detected capacity change from 0 to 512
EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback.
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
Mem abort info:
ESR = 0x0000000086000006
EC = 0x21: IABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
user pgtable: 4k pages, 48-bit VAs, pgdp=0000000113f57000
[0000000000000000] pgd=0800000136c0b403, p4d=0800000136c0b403, pud=0800000122194403, pmd=0000000000000000
Internal error: Oops: 0000000086000006 [#1] SMP
Modules linked in:
CPU: 0 UID: 0 PID: 7690 Comm: syz.0.123 Not tainted syzkaller #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 83400805 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=-c)
pc : 0x0
lr : ptp_clock_gettime+0xa4/0xb8 drivers/ptp/ptp_clock.c:114
sp : ffff80009c3d7c70
x29: ffff80009c3d7c70
x28: ffff0000f6269e80 x27: fffffffffffffffb
x26: 1fffe0001ec4d3d0 x25: ffff80008b14b6c0 x24: ffff80009c3d7ce0
x23: dfff800000000000 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000ccc57000 x19: ffff80009c3d7d00 x18: 0000000000000000
x17: 0000000000000000 x16: ffff80008b065ce0 x15: 0000000000000001
x14: 1fffe00019a15019 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000080000 x10: 00000000000000ea x9 : ffff8000a468a000
x8 : 0000000000000000 x7 : ffff800080655ba8 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80008b07a3b4
x2 : 0000000000000001 x1 : ffff80009c3d7d00 x0 : ffff0000ccc57000
Call trace:
0x0 (P)
pc_clock_gettime+0x148/0x1a8 kernel/time/posix-clock.c:258
__do_sys_clock_gettime kernel/time/posix-timers.c:1145 [inline]
__se_sys_clock_gettime kernel/time/posix-timers.c:1135 [inline]
__arm64_sys_clock_gettime+0x1b4/0x248 kernel/time/posix-timers.c:1135
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49
el0_svc_common+0x1e0/0x23c arch/arm64/kernel/syscall.c:132
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
el0_svc+0x5c/0x254 arch/arm64/kernel/entry-common.c:744
el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:763
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596
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.

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