kernel: protection fault trap, code=NUM (9)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7de01a79e4ba vmd(8): Use 32-bit direct kernel launch for b..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=15742e12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=b316677cd826c26c7b79

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4ba174832e31/disk-7de01a79.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/9704e1a48cfa/bsd-7de01a79.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/deb70bc681ca/kernel-7de01a79.xz

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

kernel: protection fault trap, code=0

Stopped at witness_checkorder+0xb5: movl 0x20(%r14),%r15d

ddb{0}> serialport: Connected to syzkaller.us-central1-b.ci-openbsd-setuid-4 port 1 (session ID: 887a4012214e621ac55009ca2f25841d90f2fbd51104b5bca3e615ab3d1c3861, active connections: 1).


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