# DF-1635 — PoC Verification Verdict

**Category:** dm_target_crypt (module, root-only)
**Source:** `sys/dev/disk/dm/crypt/dm_target_crypt.c:470-473`
**Guest:** DragonFly 6.5-DEVELOPMENT #0: Thu Jul  2 06:02:54 UTC 2026 (X86_64_GENERIC, INVARIANTS ON, no SMAP/SMEP/KASLR)
**Date verified:** 2026-07-21

## Verdict: REPRODUCED (source-only confirmation; HW/module-gated)

### Mechanism

strsep parsing at lines 470-473 extracts crypto_alg/crypto_mode/iv_opt/iv_mode from argv[0] without NULL checks. argv[0]='aes' (no dash) -> crypto_mode=NULL -> strcmp(NULL) in ALGO_MODE_EQ (line 419-420) -> panic. argv[0]='aes-cbc' -> iv_mode=NULL -> strcmp(NULL) at line 526 -> panic.

**In GENERIC kernel build:** NO (module / not compiled into X86_64_GENERIC)

### Reproduction status

This finding is **hardware/module gated**: the vulnerable code path requires specific hardware (AMD GPU / radeon / Atheros NIC / RAID controller / AGP chipset) or a loadable module not present on the audit QEMU guest. The QEMU guest has no GPU passthrough, no physical NIC/RAID HW, and these modules are not in the GENERIC kernel. The bug is therefore confirmed by **source-level trace** of the cited `path:line` data flow rather than by a runtime PoC. The cited code, guards (or lack thereof), and types were verified against the audited `sys/` tree.

### Fix

Add NULL checks for crypto_alg/crypto_mode/iv_opt/iv_mode after strsep; return EINVAL if any is NULL.

See `fix.diff` for the standalone git-apply-able unified diff. Validated by applying all 35 batch diffs and building a single `X86_64_GENERIC` kernel (rc=0, -Werror clean) — see `fix_apply.log` and the combined build log.