panic: uvm_faultWAuRnNINe:lSoPck NOT LOdWEREs nN SYSCALL NUM NUM EXIT NUM c

Status: upstream: reported on 2026/08/24 23:50
Reported-by: syzbot+fb8839eeed0d9771aaab@syzkaller.appspotmail.com
First crash: 5d14h, last: 5d14h

Sample crash report:
login: panic: uvm_faultWAuRnNINe:lSoPck NOT LOdWEREs nN SYSCALL 91 20 EXIT 0 c
Stopped at      savectx+0xae:   movl    $0,%gs:0x688
    TID    PID    UID     PRFLAGS     PFLAGS  CPU  COMMAND
 241601   1821      0           0  0x4000000    0  syz-executor
* 29533  30962      0  0x10000002          0    1  syz-executor
savectx() at savectx+0xae
end of kernel
end trace frame: 0x7d6e708a1480, count: 14
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports.  Insufficient info makes it difficult to find and fix bugs.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/24 23:49 openbsd c0485cf4f019 614e416a .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: uvm_faultWAuRnNINe:lSoPck NOT LOdWEREs nN SYSCALL NUM NUM EXIT NUM c
* Struck through repros no longer work on HEAD.