# DF-3359 -- VERDICT

**REPRODUCED** (impact=leak, confidence=certain)
Guest: DragonFly dfbsd 6.5-DEVELOPMENT DragonFly 6.5-DEVELOPMENT #0: Thu Jul  2 06:02:54 UTC 2026  root@dfbsd:/usr/obj/usr/src/sys/X86_64_GENERIC  x86_64

## Summary
rtsock builders size the DESTINATION from producer sa_len (no write overflow) but bound the SOURCE read by nothing: with the DF-3320 setup planting sin_len=200 into a live in_ifaddr (one-time root misconfiguration), an UNPRIVILEGED nobody listener received kernel heap pointers (0xfffff8004f2e5da0 etc.) via NET_RT_IFLIST (rt_msg_buffer bcopy) AND via RTM_NEWADDR/RTM_DELADDR events (rt_msg_mbuf), 12 poisoned sockaddrs per run.

## How it was verified
- Method: Live PoC on the QEMU guest (stock INVARIANTS kernel)
- Kernel references: sys/net/rtsock.c:1140-1144, sys/net/rtsock.c:1175-1180, sys/net/rtsock.c:1202-1206
- Evidence: live1.log DF-3359 section: [IFLIST]/[NEWADDR]/[DELADDR] entries with kernel pointers at offsets 56-88; unpriv listener (nobody)
- Reachability: local-unpriv where noted in the summary; root-config for tun/lagg/carp/ipfw3/gre items; remote-facing for the packet parsers (wlan harnesses model the RX/TX path verbatim because the guest has no 802.11 hardware; precedent DF-0393/DF-0594/DF-0621/DF-0350).
- Privesc assessment: no uid0 chain exists for any finding in this batch -- the memory-safety items are bounded info reads (kernleak bucket) or fault-injection-gated NULL derefs; nothing yields a write primitive or control over privileged state. The one panic-class live item (DF-3414) is root-only (SIOCIFDESTROY).

## Fix
fix_status: fixed -- Validated on the patched kernel: the combined-fix build clamps sa_len (0 or > sizeof(sockaddr_storage) -> zeroed substitute with the family preserved) in rt_msg_buffer and rt_msg_mbuf; with the fixed kernel the same planted sin_len=200 produces NO poisoned sockaddrs in NET_RT_IFLIST (see fixkernel section).
fix.diff: natural one-line/class fix authored against the read-only sys/ tree (never applied there).
Baseline vs patched (kernel): see fixkernel-*.log -- the combined-fix kernel (DF-3308+DF-3349+DF-3359+DF-3445/3446 fixes built together) was booted and the exact PoCs re-run.

## Fix status (batch validation)
Applied with the 36 sibling fix.diffs of this batch in findings/poc/_batch41/all_fixes.patch; single in-guest `make -j6 nativekernel KERNCONF=X86_64_GENERIC` completed RC=0 with zero errors under -Werror (full log: findings/poc/_batch41/fix_build8.log). Behavior A/B intentionally skipped for this Info-tier item.