# DF-1697 — PoC Verification Verdict

**Category:** mps RAID (IN GENERIC, LSI MPT-Fusion HW)
**Source:** `sys/dev/raid/mps/mps_sas_lsi.c:208-209`
**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

mpssas_fw_work topology-change loop: for(i=0;i<data->NumEntries;i++) phy=&data->PHY[i]. PHY is declared PHY[MPI2_EVENT_SAS_TOPO_PHY_COUNT=1] (mpi2_ioc.h:844). NumEntries is U8 (max 255). Loop reads 12+255*4=1032 bytes from a buffer that may be only ~16 bytes. OOB read of firmware event data.

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

Clamp the loop to 'i < data->NumEntries && i < MPI2_EVENT_SAS_TOPO_PHY_COUNT'.

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.