Syzbot: 7 years of continuous kernel fuzzing
summary
Syzbot runs syzkaller across 25 instances on arm64 and x86 VMs and reports roughly 1,000 new findings per year; since 2017 it records 17,000 findings, 6,000 mailing-list reports and 3,400 commits that mention syzbot. Reproducers exist for 64% of reported crashes while bisections succeed for ~23%. Auto-generated cause bisections increase from ~20% to ~40% coverage, subsystem tagging covers 238 subsystems, and automated LTS backport detection flags ~100 candidate commits (65% precision on 5.15, 81% on 6.1).
AI-written summary · about
chapters (16)
- 0:00Introduction to syzkaller
- 1:03Syzkaller vs syzbot distinction
- 3:57Syzbot findings and statistics
- 4:18Analysis of addressed findings
- 6:30Key predictors of bug fixes
- 9:19Bug frequency and bisection impact
- 10:03Improvements in bisection quality
- 13:17Web dashboard updates
- 16:51Bug analysis for LTS kernels
- 19:19Backporting missing fixes
- 21:48Controversial syzbot reports
- 23:11Handling low-severity reports
- 24:36How kernel can help fuzzers
- 25:43Maintainer burnout and solutions
- 26:46False positives and improvements
- 28:56Q&A session
