bpf-next build error (8)

Status: upstream: reported on 2026/09/07 07:55
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+99f4a690c25e0ae4253b@syzkaller.appspotmail.com
First crash: 2d16h, last: 2d16h
✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
985e9193 assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ bpf-next build error (8) 2026/09/09 00:49 2026/09/09 00:49 2026/09/09 01:48 243b72f1
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] bpf-next build error (8) 0 (1) 2026/09/07 07:55
Similar bugs (7)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream bpf-next build error -1 1 3081d 3081d 0/29 closed as invalid on 2018/04/03 20:00
upstream bpf-next build error (4) bpf net -1 2 1510d 1510d 0/29 auto-obsoleted due to no activity on 2022/11/19 11:25
upstream bpf-next build error (7) -1 1 12d 12d 0/29 closed as invalid on 2026/08/28 12:35
upstream bpf-next build error (5) -1 1 1350d 1346d 0/29 auto-obsoleted due to no activity on 2023/04/27 22:23
upstream bpf-next build error (2) -1 1 3072d 3072d 0/29 closed as invalid on 2018/06/14 06:16
upstream bpf-next build error (6) -1 3 808d 890d 0/29 auto-obsoleted due to no activity on 2024/10/01 18:55
upstream bpf-next build error (3) kernel -1 10 1821d 1991d 20/29 fixed on 2021/11/10 00:50

Sample crash report:
mv: cannot stat 'arch/x86/include/generated/asm/.tmp_cpufeaturemasks.h': No such file or directory

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/07 03:50 bpf-next 1b7415bf70be 4f7b22a0 .config console log report ci-upstream-bpf-next-kasan-gce bpf-next build error
* Struck through repros no longer work on HEAD.