# VERDICT — DF-1502: musycc_intr0_tx_eom derefs sch after racy NULL/!UP early-out

## Verdict

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

The bug is real and present in master DEV source at `sys/dev/misc/musycc/musycc.c:649-657`,
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 649-653: `sch = sc->chan[ch]; if (sch == NULL || sch->state != UP) { kprintf(...); }` — note the early-out only PRINTS, it does not return. Line 657 then derefs `sch->tx_last_md` even if sch is NULL or not UP. Concurrent musycc_disconnect (1347-1350) kfree(sc->mdt[ch]) and NULLs the channel after SRD+tsleep; with no locks, an in-flight EOM interrupt can race past the disconnect and deref freed/NULL sch. NULL or freed deref → panic.

## Reachability on this guest

No — musycc(4) is in LINT64 only (not GENERIC); requires a LANai/CPCI mux card. Not present in audit guest. The driver is also entirely LOCKLESS (bus_setup_intr flags=0).

## Phase 6 — escalation potential

This is a race-condition NULL/UAF deref (DoS) 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.

Make the early-out actually return (`return;` after the kprintf) so a NULL/!UP channel is never dereferenced.

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