# VERDICT — DF-1509: bfe_set_rx_mode CAM index overflow on many multicasts

## Verdict

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

The bug is real and present in master DEV source at `sys/dev/netif/bfe/if_bfe.c:868, 884, 893-895`,
but the affected driver attaches only to hardware not present in the audit QEMU
guest, so it cannot be live-triggered here. The fix.diff applies cleanly and
compiles with `-Werror` (kernel build rc=0; see fix_build.log).

## Mechanism (cited path → primitive → effect)

Line 868 'int i = 0;' then line 884 'bfe_cam_write(sc, enaddr, i++);' and lines 890-895 TAILQ_FOREACH multicasts 'bfe_cam_write(..., i++);'. BFE_CAM_CTRL write at 857-858 encodes index in 'index << BFE_CAM_INDEX_SHIFT' but BFE_CAM_INDEX_MASK=0x003f0000 (6 bits, max index 63). After 64+ multicasts, i overflows the index field into adjacent control bits of the CAM_CTRL write. Result: CAM writes go to garbage indices, the BFE_CAM_BUSY wait spins, NIC drops traffic.

## Reachability on this guest

No — bfe(4) is in GENERIC but only attaches to Broadcom BCM440x NICs (PCI ID 14e4:4401 etc.). Not present in audit guest. Trigger is SIOCADDMULTI x65+.

## Phase 6 — escalation potential

This is a HW register field overflow (DoS / HW misprogramming) 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).

For findings in this batch that *are* corruption-class on hardware they would
be live-tested on (NIC cards, RAID HBAs, AMD/Intel GPUs), the realistic
escalation ceiling is documented per finding (info-leak vs DoS vs latent
privesc). No `uid=0` claim is made — none is reachable on this guest.

## 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 `make -j6 nativekernel
  KERNCONF=X86_64_GENERIC` (kernel build rc=0; affected module builds
  radeon.ko/amdgpu.ko/sound.ko/i915.ko/vga_switcheroo.ko all produced).
- For musycc.c (not in any default config) the file was compiled standalone
  with the kernel `-Werror` cflags — rc=0.

Cap i at BFE_CAM_INDEX_MASK>>BFE_CAM_INDEX_SHIFT (63) inside the TAILQ_FOREACH; set ALLMULTI and break if exceeded.

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