syzbot


go runtime error

Status: upstream: reported syz repro on 2025/08/30 21:34
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+1c70fca55f49e85636ee@syzkaller.appspotmail.com
First crash: 1d22h, last: 1d22h
Bug presence (1)
Date Name Commit Repro Result
2025/08/31 upstream (ToT) c8bc81a52d5a syz [report] lost connection to test machine
Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 go runtime error origin:upstream 2 syz error 1 605d 730d 0/3 auto-obsoleted due to no activity on 2024/04/14 05:34
android-6-1 go runtime error origin:upstream 2 syz error inconclusive 25 122d 660d 0/2 premoderation: reported syz repro on 2023/11/11 09:24
android-5-10 go runtime error 2 22 484d 763d 0/2 auto-obsoleted due to no activity on 2024/08/02 23:33
android-54 go runtime error 2 4 470d 526d 0/2 auto-obsoleted due to no activity on 2024/08/17 11:44
android-5-15 go runtime error origin:downstream 2 syz error 9 6h29m 768d 0/2 premoderation: reported syz repro on 2023/07/26 19:25
upstream go runtime error fs 2 syz error inconclusive 23 161d 648d 0/29 upstream: reported syz repro on 2023/11/23 16:03

Sample crash report:
2025/08/30 21:33:53 executed programs: 2
fatal error: panic while printing panic value: type runtime.errorString
Connection to 10.128.1.162 closed by remote host.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/30 21:34 linux-6.1.y f89b6e15694c 807a3b61 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf go runtime error
* Struck through repros no longer work on HEAD.