# DF-1666 — PoC Verification Verdict

**Category:** drm core (module)
**Source:** `sys/dev/drm/include/linux/file.h:38-68`
**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

get_unused_fd_flags (file.h:39-50) calls REAL falloc, allocating struct file (refcount=1), inserting into global filelist, and reserving an fd. The stub put_unused_fd (file.h:65-68) is a no-op kprintf that does NOT release the fd or file. drm_syncobj_get_fd (drm_syncobj.c:407) calls get_unused_fd_flags then returns -ENOSYS (the anon_inode path is #if 0), leaking the falloc'd file refcount + fd on every call.

**In GENERIC kernel build:** NO (module / not compiled into X86_64_GENERIC)

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

Implement put_unused_fd to call kern_close(fd), releasing the leaked fd and file reference.

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.