{
 "finding_id": "DF-3231",
 "status": "not_reproduced",
 "reproduced": 0,
 "impact": "panic",
 "confidence": "likely",
 "verdict": "Not dynamically triggerable without a device I/O failure in the root-volume-header reload window: the mount holds no permanent rootvol reference, so between transactions the refcount cycles to zero, hammer_rel_volume clears ondisk, and the next transaction starter reloads the header with bread - which fails only on failing/removable media. All three starters handle that failure solely with KKASSERT(error == 0) (no-op on production builds), after which trans->rootvol NULL flows into ~25 deref sinks (vol0_next_tid, undomap, volume stats, fsid, hammer_rel_volume). Fault injection is unavailable on this guest. Fix converts the three assertions into explicit panics with a message on all builds; compile-validated.",
 "exploit_chain": "",
 "evidence": "VERDICT.md walk over hammer_transaction.c:53/:79/:109 and the release-at-zero path from hammer_vfsops.c:773",
 "kernel_refs": [
  "sys/vfs/hammer/hammer_transaction.c:53",
  "sys/vfs/hammer/hammer_transaction.c:79",
  "sys/vfs/hammer/hammer_transaction.c:109"
 ],
 "poc_changes": "",
 "attempts": 2,
 "guest_uname": "DragonFly dfbsd 6.5-DEVELOPMENT #0: Thu Jul 2 06:02:54 UTC 2026 root@dfbsd:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64",
 "runtime_sec": 60,
 "guest_dirty": 0,
 "build_cmd": "n/a",
 "run_cmd": "n/a (needs induced device I/O error in the header-reload window)",
 "code_hash": "",
 "notes": "",
 "recommended_fix": "explicit panic on root-volume reload failure on all builds"
}