Coverage-guided fuzzing (CGF) is a feedback-driven software/hardware testing technique that uses execution feedback, most commonly code coverage, to steer input mutation toward unexplored program or design behavior. Public research describes CGF as effective across software applications, but warns that higher coverage does not necessarily imply better fault detection: triggering a bug requires both reaching a path and entering a relevant state on that path. Active research investigates alternative feedback signals (mutation scores, microcode-level feedback, contextual-bandit seed reuse, coverage-guided aging) to escape coverage plateaus and to better couple coverage with bug detection. The technique has been applied to processor/hardware verification (DifuzzRTL, TheHuzz, RFUZZ, Cascade, ChatFuzz, FuSS, GoldenFuzz, ReFuzz, Fuzzilicon) and to LLM-based multi-agent systems (FLARE).
First seen5/25/2026
Last seen9/28/2026
Evidence83 chunks
Wikiv9
01
WIKI
Overview
Coverage-guided fuzzing (CGF) is a testing technique that uses execution feedback, commonly code coverage, to guide input mutation toward inputs that explore more program behavior. Public research describes CGF as an effective technique that has detected many bugs across software applications and as a technique that focuses on maximizing code coverage during fuzzing. However, the same research cautions that higher coverage does not necessarily imply better fault detection: triggering a bug can require both exercising a particular path and reaching an interesting program state on that path. [CGF definition and coverage caveat]
[1]CGF is effective for finding bugs across software applications but higher coverage does not imply better fault detection because triggering a bug requires reaching interesting program states, not just exercising paths.Investigating Coverage Guided Fuzzing with Mutation Testing
[3]Cascade achieves the same control-register coverage as DifuzzRTL in 30 minutes (15 minutes with a pre-generated corpus) versus 48 hours for DifuzzRTL on the legacy Rocket core, corresponding to 97x and 186x speedups.Cascade: CPU Fuzzing via Intricate Program Generation
[4]Cascade compares against DifuzzRTL using control-register coverage, against RFUZZ using multiplexer-select coverage, and additionally reports the commercial-simulator metrics used by TheHuzz (branches, conditions, expressions, FSM states and transitions, statements, toggles).Cascade: CPU Fuzzing via Intricate Program Generation
[5]Cross-level RISC-V processor verification via endless randomized instruction stream generation with coverage-guided aging uses an ISS as a functional reference, updates coverage continuously from ISS state, and supports arbitrary combinations of load/store and CSR instructions as well as infinite loops; experiments on the 32-bit pipelined MINRES The Good Core (TGC) show more regular coverage distribution via coverage-guided aging.RISC-V Processor Verification with Coverage-guided Aging
[6]Google's open-source RISC-V Design Verification framework uses constraint-based specification in SystemVerilog, co-simulation against an ISS, and symbolic execution but does not employ runtime coverage information, relying instead on simple randomized test generation that struggles to continuously achieve broad and deep test coverage in endless instruction streams.RISC-V Processor Verification with Coverage-guided Aging
[7]FLARE applies coverage-guided fuzzing to LLM-based multi-agent systems, extracting specifications and behavioral spaces from agent definitions to build test oracles, and reports 96.9% inter-agent coverage, 91.1% intra-agent coverage, and 56 previously unknown failures across 16 open-source applications.FLARE: Agentic Coverage-Guided Fuzzing for LLM-Based Multi-Agent Systems