[moderation] panic: runtime error: invalid memory address or nil pointer dereference (5)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 06dc10eae55b Merge tag 'fbdev-for-6.6-rc7' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=109f73ad680000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c2b0838e2a16cba
dashboard link: https://syzkaller.appspot.com/bug?extid=6abc66114c9998de4b19
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/54a173fe638f/disk-06dc10ea.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/501195b07c64/vmlinux-06dc10ea.xz
kernel image: https://storage.googleapis.com/syzbot-assets/10925166d81e/bzImage-06dc10ea.xz

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

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x540b05]

goroutine 10 [running]:
github.com/google/syzkaller/prog.foreachArgImpl({0xcf45f0?, 0xc026f18c10?}, 0xc017c811c0, 0xc0002afa10)
/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:147 +0x385
github.com/google/syzkaller/prog.foreachArgImpl({0xcf45f0?, 0xc02a790d80?}, 0xc017c811c0, 0xc0002afa10)
/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:151 +0x3ba
github.com/google/syzkaller/prog.foreachArgImpl({0xcf45f0?, 0xc02a790c20?}, 0xc017c811c0, 0xc0002afa10)
/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:151 +0x3ba
github.com/google/syzkaller/prog.foreachArgImpl({0xcf4630?, 0xc014852060?}, 0xc017c811c0, 0xc0002afa10)
/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:168 +0x2ce
github.com/google/syzkaller/prog.ForeachArg(0xc023a71ae0, 0xc02a376800?)
/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:127 +0xde
github.com/google/syzkaller/prog.(*Target).CallContainsAny(0x411104?, 0x0?)
/syzkaller/gopath/src/github.com/google/syzkaller/prog/any.go:128 +0x50
main.signalPrio(0xa341c0?, 0xc00007a960?, 0x8130d88c?)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:612 +0x4e
main.(*Fuzzer).checkNewCallSignal(0xc000228600, 0xc0002afba8?, 0xc0002afbc8, 0xc01fabc780?)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:592 +0x45
main.(*Fuzzer).checkNewSignal(0xc000228600, 0x484b5e?, 0xc019ca8120)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:583 +0x167
main.(*Proc).execute(0xc0259341c0, 0x11?, 0x12?, 0xc0002afe08?, 0x1?)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/proc.go:259 +0x74
main.(*Proc).executeAndCollide(0xc0259341c0, 0xabe1c9?, 0xc02631e300?, 0xc0002afe08?, 0xc025934040?)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/proc.go:284 +0x27
main.(*Proc).smashInput(0xc0259341c0, 0xc012ed51e0)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/proc.go:221 +0x1d4
main.(*Proc).loop(0xc0259341c0)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/proc.go:78 +0xf2
created by main.main
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:310 +0x15e5
SeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000200000000 = 8192 MiB
CPUs found: 2 Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID a43267f0-55bb-60fb-9ba6-3e5783d82cc8
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f2870: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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.