# VERDICT — DF-1527: i915_request postfix uninitialized on RCU-reuse

## Verdict

**INCONCLUSIVE (HW/module gated) — source-level confirmed, fix validated.**

The bug is real and present in master DEV source at `sys/dev/drm/i915/i915_request.c:786-791, 1082, 1033-1037`, but
the affected driver attaches only to hardware not present in the audit QEMU
guest (only virtio+PIIX3 PCI devices, no AMD/Intel GPUs, no ath NICs, no
AdvanSys SCSI, no mfi/tws/mrsas RAID, etc.), so it cannot be live-triggered
here. The `fix.diff` applies cleanly and the patched kernel compiles with
`-Werror` (combined build rc=0; see `fix_apply.log`).

## Mechanism (cited path → primitive → effect)

i915_request_alloc hand-clears global_seqno/signaling.wait.seqno/file_priv/batch/capture_list but OMITS postfix (comment: Do not use kmem_cache_zalloc). Request slab is SLAB_TYPESAFE_BY_RCU, NOT zeroed on realloc. postfix is only assigned at 1082 in i915_request_add; if i915_request_skip runs before that with a stale postfix, line 1033 if(rq->postfix < head) memset(vaddr+head, 0, ring->size - head) clears wrong region.

## Reachability on this guest

No — `sys/dev/drm/i915/i915_request.c:786-791` is in a driver/module that only attaches
to hardware absent from the audit guest. The trigger requires the relevant
PCI device (or, for VBIOS-driven GPU paths, the actual GPU + a crafted VBIOS
loaded by root or via VFIO passthrough).

## Phase 6 — escalation potential

This is a Use of uninitialized value primitive. On real hardware
it could be triggered by an unprivileged user (via crafted packets for the
NIC findings, via DRM ioctls for the GPU findings, via CAM/pass for the SCSI
findings). On **this guest** there is no live primitive to convert. Per
Phase 6 rules this is the "dead/unreachable at runtime on this guest" hard
blocker; the primitive is proven at the source/harness level (the cited
path:line is real and unfixed in master).

Realistic impact ceiling on suitable HW: **kernel memory corruption (memset on wrong ring region) or info leak of stale ring contents**.

## Phase 8 — fix validation

`fix.diff` is a minimal, targeted fix at the root cause confirmed above.

- **Applied cleanly** with `patch -p1 --forward` (verified in `fix_apply.log`).
- **Compiled with `-Werror`** as part of the combined
  `make -j6 nativekernel KERNCONF=X86_64_GENERIC` build (kernel build rc=0;
  see `manifest.json`).
- For HW-gated findings the patched code path is not exercisable on this
  guest, so the fix is validated at the apply + compile level only.

Fix approach: Initialise rq->head/rq->infix/rq->postfix/rq->tail to 0 alongside the other hand-clears in i915_request_alloc.

## PoC changes

Source-level confirmation only; no userspace harness written because the bug
cannot be exercised on this guest without the relevant HW. The placeholder
`build.sh`/`run.sh` echo pointers to `VERDICT.md` and the module/kernel
rebuild path.