syzbot


protection fault in Xosyscall

Status: upstream: reported on 2024/04/23 10:52
Reported-by: syzbot+a770f2443225bc887c8c@syzkaller.appspotmail.com
First crash: 27d, last: 27d

Sample crash report:
[ 159.8215152] fatal protection fault in supervisor mode
[ 159.8215152] trap type 4 code 0 rip 0xffffffff802000b0 cs 0x8 rflags 0x10046 cr2 0x624040 ilevel 0 rsp 0xffff9c825dd49f00
[ 159.8215152] curlwp 0xffff9c801343d780 pid 1674.1674 lowest kstack 0xffff9c825dd422c0
kernel: protection fault trap, code=0
Stopped in pid 1674.1674 (syz-executor.2) at    netbsd:Xosyscall+0xa0:  addb    %al,0(%rax)
?
Xosyscall() at netbsd:Xosyscall+0xa0
[ 159.8215152] prevented access to 0x623718 (SMAP)
[ 159.8215152] fatal page fault in supervisor mode
[ 159.8215152] trap type 6 code 0x1 rip 0xffffffff80980e33 cs 0x8 rflags 0x10282 cr2 0x623718 ilevel 0x8 rsp 0xffff9c825dd48b70
[ 159.8215152] curlwp 0xffff9c801343d780 pid 1674.1674 lowest kstack 0xffff9c825dd422c0
kernel: page fault trap, code=0
Faulted in DDB; continuing...

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/23 10:51 netbsd 8a12906d648f 21339d7b .config console log report [disk image] [netbsd.gdb] ci2-netbsd protection fault in Xosyscall
* Struck through repros no longer work on HEAD.