Commit abef37a
serde_2026: dedicated panic-finder fuzz target
The existing serde-2026 fuzzer is a roundtrip checker — it Corpus::Reject's
any blob that fails to fully decode, which means libfuzzer never accumulates
seeds for the "almost-decodes-then-aborts" failure mode. The historical
de.rs OOM (tiny blob declaring instruction_count = 2^54, abort in
Vec::with_capacity before any instruction is read) lives in exactly that
bucket and was not surfaced by the existing fuzzer; it took Cursor's
static analysis to find.
Add serde-2026-panic, which feeds arbitrary bytes to all three public
entry points — deserialize_2026_body, node_from_bytes_serde_2026,
serialized_length_serde_2026 — under both strict={false,true}, and
asserts only that nothing panics, aborts, or overflows the stack.
Result::Err is fine; SIGABRT, unwinding panic, or SO is a bug.
CI's existing fuzz job auto-discovers targets via `cargo +nightly fuzz list`
and gives each 30s, so no workflow change is needed.
Co-authored-by: Cursor <cursoragent@cursor.com>1 parent 6ac4265 commit abef37a
2 files changed
Lines changed: 47 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
160 | 160 | | |
161 | 161 | | |
162 | 162 | | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
0 commit comments