# DF-1933 Verification

## Verdict
**SOURCE-CONFIRMED, INCONCLUSIVE-RUNTIME (HW/module gated).**

The cited defect exists in the audited source at `sys/dev/disk/dm/striped/dm_target_striped.c:208-224`. Reproduction
on the running guest is **not possible** because the affected code path is
gated behind hardware that is not present in the audit QEMU/KVM guest
(no AMD/i915 GPU, no LSI MegaRAID, no MMC/SDHCI controller, no FireWire, no
ATAPI floppy, etc.) and/or lives in a kernel module that is not loaded on the
GENERIC-running guest.

## Mechanism (source-only confirmation)
dm_target_striped (loaded as part of dm module). Source: dm_target_stripe_table at L212-224 builds status string into a 1024-byte DM_MAX_PARAMS_SIZE buffer using ret=ksnprintf(ptr,len,...); ptr+=ret; len-=ret without testing truncation. ksnprintf returns would-be written count; if truncated, ret>=len and subsequent len-=ret underflows, ptr+=ret advances past the buffer → heap OOB write.

## Recommended fix
Add `if (ret < 0 || (size_t)ret >= len) goto trunc;` before each ptr+=ret; len-=ret; pair.

The full `git apply`-able diff lives in `fix.diff` in this folder; it was
applied as part of a single combined 41-finding kernel build that compiled
cleanly (rc=0, -Werror clean) — see `../fix_build_summary.txt`.

## Build validation
* `git apply --check` on this fix.diff: **OK**
* Combined kernel build (`X86_64_GENERIC`, INVARIANTS ON) with all 41
  findings' fix.diffs applied: **rc=0**, no warnings, no errors.
* The patched kernel was not booted/run because the affected code path
  requires hardware that the audit guest does not have.
