# DF-1615 — PoC Verification Verdict

**Category:** twe RAID (IN GENERIC, 3ware HW)
**Source:** `sys/dev/raid/twe/twe_freebsd.c:494-509`
**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

twe_suspend calls crit_exit() at line 506 with NO matching crit_enter() anywhere in twe_suspend or its callees (verified: only crit_* call in entire sys/dev/raid/twe/). This unbalances the crit nesting count, corrupting interrupt-state tracking.

**In GENERIC kernel build:** YES

### 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

Remove the stray crit_exit() from twe_suspend.

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.