From an OSS-Fuzz Report to LKML Patch Submission: A Hands-on Journey
Talkat LinuxCon @ Open Source Summit Japan 2023 · on Tuesday, 2023-12-05· at 14:50· Conference Room 1 (3F Level), Ariake Central Tower Hall + Conference, 3-7-18, Ariake, Koto-ku·
summary
Walks from OSS-Fuzz report 40868/40957 to a Linux kernel patch: uses OSS-Fuzz reproducers to reproduce crashes locally, builds with AddressSanitizer, identifies a heap buffer overflow (CVE-2021-45940) where section count is zero, replaces the field with elf_getSectionHeaderNumber, rebuilds and confirms the sanitizer no longer reports the bug. Prepares git-format-patch with Certificate of Origin, posts to the BPF mailing list with proper prefix/version, iterates (v2) after maintainer review, and lands the fix.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:42OSS-Fuzz reports and BPF issues
- 2:28What is OSS-Fuzz
- 5:19Setting up OSS-Fuzz
- 9:58Diagnosing with sanitizer reports
- 12:30Submitting a fix to the Linux kernel mailing list
- 13:58Patch email requirements
- 17:12Generating patch email
- 21:16Configuring email
- 23:02Addressing feedback
- 24:47End-to-end process
- 25:57Q&A
related talks
39mThe Life of a Kernel Bugfix
01h 39mFuzzing in the open: Integrate your project in OSS-Fuzz for continuous fuzzing
46mBypass Kernel Barriers: Fuzzing Linux Kernel in Userspace With LKL
20mKFuzzTest: Targeted Fuzzing of Internal Kernel Functions
25mHow fuzzing helps to find bugs
24mWhy you should be using automated fuzzing to test for security issues in your code
45mFrom an Idea to a Patch in the Linux Mainline
09mLinux Kernel Bug Fixing Project