ci: Drop libFuzzer from msan fuzz task
What the developer wrote
Authored by MarcoFalke
ci: Drop libFuzzer from msan fuzz task
What changed, and why it matters
This commit changes a single CI (continuous integration) test configuration file. It removes 'fuzzer' from the list of sanitizers used in an MSan (MemorySanitizer) fuzzing task, leaving only 'memory'. This is a build/test pipeline adjustment, not a change to Bitcoin Core's runtime code, wallet logic, networking, or consensus rules. There is no indication of a security vulnerability being fixed.
No security action required. Review as a normal CI maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies ci/test/00_setup_env_native_fuzz_with_msan.sh, changing -DSANITIZERS=fuzzer,memory to -DSANITIZERS=memory. This drops libFuzzer from the MSan CI fuzz task, likely because the fuzzer harness is now provided separately or the build configuration was reorganized. The change affects only CI environment setup and does not alter source code, APIs, or cryptographic/consensus behavior.
Changed components
ci/test/00_setup_env_native_fuzz_with_msan.shInspect captured patch +1 / −1
diff --git a/ci/test/00_setup_env_native_fuzz_with_msan.sh b/ci/test/00_setup_env_native_fuzz_with_msan.sh
index 0d906057..7529bbc6 100755
--- a/ci/test/00_setup_env_native_fuzz_with_msan.sh
+++ b/ci/test/00_setup_env_native_fuzz_with_msan.sh
@@ -25,7 +25,7 @@ export BITCOIN_CONFIG="\
-DCMAKE_C_FLAGS_DEBUG='' \
-DCMAKE_CXX_FLAGS_DEBUG='' \
-DBUILD_FOR_FUZZING=ON \
- -DSANITIZERS=fuzzer,memory \
+ -DSANITIZERS=memory \
-DAPPEND_CPPFLAGS='-DBOOST_MULTI_INDEX_ENABLE_SAFE_MODE -U_FORTIFY_SOURCE' \
"
export USE_INSTRUMENTED_LIBCPP="MemoryWithOrigins"
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.