KASAN: invalid memory access in sysctl_sysvipc

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d540b1bf3d7f kasan: pool describe: only the owning pool ma..
git tree: https://github.com/blackgnezdo/openbsd-src.git syzbot-kasan
console output: https://syzkaller.appspot.com/x/log.txt?x=11670c32580000
kernel config: https://syzkaller.appspot.com/x/.config?x=85e25e37d09e1b88
dashboard link: https://syzkaller.appspot.com/bug?extid=70f040b6548de270e4ef

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/954c7d6467f3/disk-d540b1bf.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/81e27dfd971c/bsd-d540b1bf.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4416bdc3d26b/kernel-d540b1bf.xz

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

panic: Caught invalid memory access at ffff800001ea83b0 size 104 op 1
Starting stack trace...
panic(ffffffff846367f9) at panic+0x25b sys/kern/subr_prf.c:229
kasan_memcpy(ffff800001ea83b0,ffff800001e4e5c8,68) at kasan_memcpy+0x1ec
sysctl_sysvipc(ffff80002f778b28,1,200000000040,ffff80002f778b00) at sysctl_sysvipc+0x746 sys/kern/kern_sysctl.c:2781
kern_sysctl_dirs(33,ffff80002f778b28,1,200000000040,ffff80002f778b00,0,1,1ffff00005eef0dc) at kern_sysctl_dirs+0x30f sys/kern/kern_sysctl.c:429
kern_sysctl(ffff80002f778b24,2,200000000040,ffff80002f778b00,0,0,ffff80002f778d80) at kern_sysctl+0x1ce sys/kern/kern_sysctl.c:529
sys_sysctl(ffff800045ff6550,ffff80002f778d80,ffff80002f778ce0) at sys_sysctl+0x54f sys/kern/kern_sysctl.c:309
syscall(ffff80002f778d80) at syscall+0x1089 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80002f778d80) at syscall+0x1089 sys/arch/amd64/amd64/trap.c:783
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xa4f10382af0, count: 249
End of stack trace.


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