fuzz/fuzz_decode.cc exists with a seed corpus (fuzz/corpus) and fuzz/run_fuzz.sh runs it locally, but CI (.github/workflows/ci.yml) does not exercise the fuzzers.
Good first issue: add a short-budget libFuzzer job to CI (a few minutes per PR), commit interesting corpus entries, and add a second fuzz target for the SACK-block parser, which is the most attacker-shaped input surface.
Bonus: a crash reproducer template in CONTRIBUTING.md.
fuzz/fuzz_decode.cc exists with a seed corpus (fuzz/corpus) and fuzz/run_fuzz.sh runs it locally, but CI (.github/workflows/ci.yml) does not exercise the fuzzers.
Good first issue: add a short-budget libFuzzer job to CI (a few minutes per PR), commit interesting corpus entries, and add a second fuzz target for the SACK-block parser, which is the most attacker-shaped input surface.
Bonus: a crash reproducer template in CONTRIBUTING.md.