panic: runtime error: invalid memory address or nil pointer dereference (8)

7 views
Skip to first unread message

syzbot

unread,
Jun 11, 2022, 9:21:21 AM6/11/22
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c0a6a244667a More %i vs %d cleanup
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=12fb1cd7f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=9869adfcfa38f3f8017c

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

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

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

goroutine 29 [running]:
github.com/google/syzkaller/prog.newState(0x0, 0xc00023b740, {0xc00162e000, 0x1a47, 0x1c00})
/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:47 +0x53
github.com/google/syzkaller/prog.analyze(0xc00023b740, {0xc00162e000, 0x1a47, 0x1c00}, 0xc0016203c0, 0x0)
/syzkaller/gopath/src/github.com/google/syzkaller/prog/analysis.go:28 +0x65
github.com/google/syzkaller/prog.(*mutator).insertCall(0xc0005abea0)
/syzkaller/gopath/src/github.com/google/syzkaller/prog/mutation.go:140 +0xe5
github.com/google/syzkaller/prog.(*Prog).Mutate(0xc0016203c0, {0x743d88, 0xc00033a120}, 0x14, 0xc00023b740, {0xc00162e000, 0x1a47, 0x1c00})
/syzkaller/gopath/src/github.com/google/syzkaller/prog/mutation.go:45 +0x2ee
main.(*Proc).loop(0xc0004c84c0)
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/proc.go:95 +0x455
created by main.main
/syzkaller/gopath/src/github.com/google/syzkaller/syz-fuzzer/fuzzer.go:300 +0x1ce9



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

Greg Steuck

unread,
Jun 16, 2022, 9:56:00 PM6/16/22
to syzbot, 'Dmitry Vyukov' via syzkaller-openbsd-bugs
#syz invalid
Reply all
Reply to author
Forward
0 new messages