arXiv paper· software engineering (fuzzing / systems security)· method paper

CAROL: Context-Aware Online Learning for Fuzzer Scheduling

Zirui Liu, Mengfan Xu, Juan Zhai, Shenglong Yao, Shiqing Ma

cs.SE · cs.LG

Quick verdict

Claims context-aware online learning beats fuzzer-ensemble schedulers (+11.8% on Magma); evaluation is rigorous, but resolved per-target gains are narrow.

Summary

CAROL targets ensemble fuzzing, where a scheduler divides CPU time among fuzzers sharing a seed store. The authors first measure two limitations of existing schedulers (BandFuzz, AUTOFZ, LEGION): rankings from consecutive reward windows are no more correlated (Kendall 0.081 vs 0.085 within-window) than estimation noise allows, and a context-to-reward weighting transferred from eight targets predicts the ninth worse than one learned on the current target, on eight of nine Magma targets. They propose two schedulers: Method I classifies each fuzzer as rising or rotting via a Mann-Kendall trend test and applies a phase-specific estimator; Method II, the shipped CAROL, learns a per-fuzzer reward model over 15 dispatch-loop context signals using random Fourier features and ridge regression with Gaussian-perturbed selection. Across nine Magma targets with ten 24-hour campaigns per cell (1,180 campaigns), Method II sums 34.20 mean unique bugs versus 28.40/28.80/29.00 for the three baselines, +11.8% over the strongest-baseline composite (30.60) and above the best-single-fuzzer oracle (32.00). Ablations show removing context (28.00, below BandFuzz) or exploration (25.20) eliminates the gain. The same configuration finds 120 previously unknown crashing defects in five C++ programs, disclosed responsibly. Limitations: after Holm correction only libtiff and sqlite3 resolve against the strongest baseline; no equal-share baseline exists; baselines are reimplementations; four of six fuzzers are AFL-lineage; the motivating statistics correlate weakly (0.20/0.00) with gains.

Review complete

Assessment at a glance

software engineering (fuzzing / systems security)

5

risk flags identified

● high 0

● medium 3

● low 2

Reproducibility readinesshigh
Code & data availableyes
Review confidencehigh
AI text signal0/20 passages flagged
Deep research viableCode-reproducible

5 strengths · 5 weaknesses · 5 author questions

AI text signal = Binoculars zero-shot detector score over 20 sampled passages (Fast-DetectGPT co-reported) — absence does not prove human authorship, and a flag does not imply misconduct.

Levels reflect verification complexity — not a quality score. Evolve never rates your paper.

Key claims under review

  • Past-reward summaries fail to capture fuzzer ranking evolution: adjacent-window Kendall correlation (0.081) is statistically indistinguishable from within-window self-agreement (0.085) after accounting for estimation noise (§2.2).
  • The context-to-reward weighting is target-specific: a model trained on eight targets predicts the held-out target worse than a within-target model on eight of nine targets, ranking a different fuzzer first on a median 51.0% of decisions (§5.1).
  • CAROL (Method II) triggers more unique Magma bugs than BandFuzz/AUTOFZ/LEGION on every target where results differ and fewer on none, summing 34.20 vs 28.40/28.80/29.00 and +11.8% over the strongest-baseline composite (30.60), also exceeding the best-single-fuzzer oracle (32.00).
  • Both context and randomized exploration are necessary: replacing context with an intercept yields 28.00 (below BandFuzz) and removing exploration yields 25.20 (§7).
  • The unchanged Method II configuration finds 120 previously unknown crashing defects in five C++ programs, all reproduced on uninstrumented builds and reported through maintainers' channels (§6.5).

Strengths

  • Unusually rigorous evaluation protocol

    1,180 campaigns / 169,920 core-hours; ten 24h campaigns per cell (§6.1); Vargha-Delaney A12 plus Mann-Whitney U with Holm correction per nine-target family, exact sign tests, and pair-specific permutation resolution thresholds instead of bare p-values (§6.1, §A.25).

  • Conspicuously honest negative results

    The intercept-only ablation scores 28.00, below BandFuzz's 28.40 (§7); the regret bound is stated as uninformative at the evaluated horizon (§A.17); the two motivating statistics correlate only 0.20/0.00 with per-target gain (§A.13); the regret bound and constant-sensitivity limits are reported in the authors' own voice.

  • Theory cleanly scoped and matched to practice

  • Real-world validation with disciplined disclosure

  • Component-level ablations tie design to outcome

Weaknesses

  • Resolved gains are narrow against the strongest baseline

  • Saturated targets inflate the dominance claim

  • Motivation-outcome disconnect

  • Reimplemented baselines and a missing sanity comparator

  • Untested hyperparameter and configuration sensitivity

Full Review Report

$1.99 · one-time

Unlock the complete preliminary analysis Evolve produced for this paper.

Report preview

Scope & Claims

CAROL (arXiv 2609.06772, cs.SE/cs.LG) is a method paper on **ensemble fuzzer scheduling**: given six fuzzers sharing a seed store, decide at every free core which fuzzer runs next. It makes three claims: (1) existing schedulers rank fuzzers from past-reward summaries whose ordering information is indistinguishable from noise (§2.2: adjacent-window Kendall correlation 0.081 vs 0.085 within-window self-agreement, paired difference 0.004, CI [-0.08, 0.09]); (2) the context-to-reward weighting is target-specific (§5.1: transfer from eight targets loses on eight of nine, top-ranked fuzzer differs on a median 51.0% of decisions); (3) learning the weighting online from 15 dispatch-loop signals beats BandFuzz, AUTOFZ and LEGION on Magma and transfers to real software (120 new defects, §6.5).

The remaining sections cover Methodology Assessment, Statistical Evidence, Results & Reproducibility, Limitations & Risks, and Verdict & Recommendations.

  • All 5 strengths & 5 weaknesses, analyzed in detail
  • 5 risk flags with severity, section & reviewer questions
  • Methods & statistical evidence assessment
  • 5 questions a peer reviewer would ask
  • Full six-dimension evaluation report & recommendations

One-time purchase · this paper only

One-time purchase, this paper only. AI-generated preliminary analysis — not peer review.

Frequently asked questions

What is CAROL?

CAROL is a scheduler for ensemble fuzzing: when several fuzzers share one seed store and a pool of CPU cores, CAROL decides which fuzzer runs next by online-learning, during the campaign itself, a model that predicts each fuzzer's next-turn reward from 15 signals of its current situation (waiting time, plateau duration, reached code, estimate uncertainty, etc.).

How much better is CAROL than BandFuzz?

On nine Magma targets with ten 24-hour campaigns per configuration, CAROL sums 34.20 mean unique bugs versus BandFuzz's 28.40 (+20.4%), AUTOFZ's 28.80 and LEGION's 29.00. Against the strongest baseline chosen per target (composite 30.60) the gain is 11.8%; after statistical correction, the per-target gains resolve on libtiff and sqlite3.

Did CAROL find real vulnerabilities?

Yes: run unchanged on five widely used C++ programs (MNN, Arm NN, Krita, ncnn, FreeCAD), it produced 120 previously unknown crashing defects, each reproduced five-out-of-five on uninstrumented builds and reported to maintainers through each project's security channel; 42 have public tracker issues.

Is the code and data available?

The paper ships an anonymous four-part artifact (source, configs, per-campaign records, analysis scripts) via anonymous.4open.science, intended to regenerate Table 1 and the offline analyses; authors state it will move to a stable public location on acceptance.

About this review

This is an AI-generated preliminary review by Evolve.Pub, produced from the openly available text of the paper. It is not peer review and does not represent the authors' views. The canonical record of the paper is at the publisher link above.

  • The provided text is a sampled excerpt with explicit '[...sampling gap...]' markers (e.g., part of §4, the tail of §6.2, §A.1-A.2, §A.22, Table 13 header); judgments avoid asserting absence of content in those skipped regions.
  • The metadata abstract is itself cut mid-sentence ('Removing context eliminates'); the complete in-paper abstract was used instead.

Go deeper on this paper

Wrote a paper? Stress-test it before reviewers do.

Upload your manuscript for the same structured scrutiny — reasoning, statistics, evidence, figures, and reproducibility.

Scan your paper
CAROL: Context-Aware Online Learning for Fuzzer Scheduling | Evolve.Pub