panic: malloc: allocation too large, type = NUM, size = ADDR (5)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ceb7068b172a regress/rpki-client: drop support for eopenss..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=178440a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=eef7ac9dfe338eeaec7c

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/45ba055b8c42/disk-ceb7068b.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/4388434aad1e/bsd-ceb7068b.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/99b415138db7/kernel-ceb7068b.xz

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

panic: malloc: allocation too large, type = 31, size = 4294970604
Starting stack trace...
panic(ffffffff833a1150) at panic+0x1d0 sys/kern/subr_prf.c:229
malloc(100000cec,1f,1) at malloc+0xcf4 sys/kern/kern_malloc.c:334
sys_semop(ffff80002a34e7e8,ffff80003c4b6fe0,ffff80003c4b6f30) at sys_semop+0x234 sys/kern/sysv_sem.c:564
syscall(ffff80003c4b6fe0) at syscall+0xb08 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80003c4b6fe0) at syscall+0xb08 sys/arch/amd64/amd64/trap.c:748
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x460f14918a0, count: 252
End of stack trace.



OpenBSD/amd64 (Amnesiac) (tty00)



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