LLVMFuzzerTestOneInput

CodeArtifact

LLVMFuzzerTestOneInput is the target-side input callback used by libFuzzer for in-process coverage-guided fuzzing. The function is defined by the device or software under test, is called repeatedly by libFuzzer with generated byte-stream inputs, and typically returns 0 after processing an input.

First seen 5/28/2026

Last seen 6/8/2026

Evidence 4 chunks

Wiki v1

WIKI

Overview

LLVMFuzzerTestOneInput is the input interface function that a device or software under test provides to libFuzzer. In the cited coverage-guided fuzzing workflow, libFuzzer is linked with the device under test (DUT) for in-process fuzzing and calls this interface function repeatedly during the fuzzing process. The function receives generated input data, lets the DUT process it, and returns 0 to indicate that the input has been processed.

Role in libFuzzer

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

2 connections

libFuzzer ← uses 100% 4e

LLVMFuzzerTestOneInput is the interface function that libFuzzer calls repeatedly to pass inputs to the DUT.

libFuzzer part of → 100% 2e

LLVMFuzzerTestOneInput is the interface function defined in the DUT that libFuzzer calls.

LINKED ENTITIES

1 links

libFuzzer USES Extracted graph relationship

CITATIONS

5 sources

5 citations — click to expand

[1] LLVMFuzzerTestOneInput is the DUT-provided input interface function called repeatedly by libFuzzer during fuzzing. Verifying Instruction Set Simulators using Coverage-guided Fuzzing

[2] libFuzzer is LLVM-based, generates binary byte-stream inputs to maximize DUT code coverage, and uses clang instrumentation for coverage feedback. Verifying Instruction Set Simulators using Coverage-guided Fuzzing

[3] libFuzzer is linked with the DUT for in-process fuzzing and passes inputs through specific interface functions. Verifying Instruction Set Simulators using Coverage-guided Fuzzing

[4] The shown LLVMFuzzerTestOneInput harness pattern includes optional one-time initialization, input processing, and returning 0 after processing. Verifying Instruction Set Simulators using Coverage-guided Fuzzing

[5] In the RISC-V ISS workflow, libFuzzer-generated byte streams are interpreted as instruction sequences, embedded into ELF testcases, executed on an instrumented simulator under test, and compared with a reference result. Verifying Instruction Set Simulators using Coverage-guided Fuzzing