{
 "finding_id": "DF-3265",
 "status": "not_reproduced",
 "reproduced": 0,
 "impact": "panic",
 "confidence": "certain",
 "verdict": "Code-proven and not injectable: for PFSTATE_STACK_GLOBAL states (every RDR translation) pf_state_key_attach holds pf_global_statetbl_lock exclusively, and if the pf_state_item kmalloc(M_NOWAIT) fails the error path calls pf_state_key_detach, which re-acquires the same lock exclusively; the lock is initialized without LK_CANRECURSE so lockmgr panics with locking against myself - a memory shortage on the packet path becomes a remote-triggered panic. Forcing a mid-function M_NOWAIT failure under memory pressure at the exact allocation is not practical on this guest. Fix releases the global lock before the detach and re-acquires it; compile-validated.",
 "exploit_chain": "",
 "evidence": "VERDICT.md walk over pf.c:911-917 and pf_state_key_detach at :955-985",
 "kernel_refs": [
  "sys/net/pf/pf.c:915-918",
  "sys/net/pf/pf.c:955-985"
 ],
 "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 (cannot force the M_NOWAIT failure)",
 "run_cmd": "n/a",
 "code_hash": "",
 "notes": "",
 "recommended_fix": "drop and re-acquire the global lock around the error-path detach"
}