BUG: workqueue function defense_work_handler changed kcov_mode from NUM to NUM

Status: auto-obsoleted due to no activity on 2026/07/29 06:01
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+e6686317bd9fe911591a@syzkaller.appspotmail.com
First crash: 103d, last: 103d
▶ ▼ ✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
2dd167cc assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ BUG: workqueue function defense_work_handler changed kcov_mode from NUM to NUM 2026/05/26 03:55 2026/05/26 03:55 2026/05/26 05:00 c69befb3
▶ ▼ Discussions (2)
Title Replies (including bot) Last reply
[PATCH] kcov: fix potential kcov_mode corruption under CONFIG_PREEMPT_RT 5 (5) 2026/05/21 08:38
[PATCH (draft)] kcov: fix potential kcov_mode corruption under CONFIG_PREEMPT_RT 2 (2) 2026/05/04 15:39

Sample crash report:
BUG: workqueue function defense_work_handler changed kcov_mode from 0 to 2

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/30 06:00 linux-next 0787c45ea08a 005438fc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce BUG: workqueue function defense_work_handler changed kcov_mode from NUM to NUM
* Struck through repros no longer work on HEAD.