# DF-2512 — Admin request leak on failed Identify NS exhausts pool -> KKASSERT panic

## Verdict
NOT REPRODUCED (hardware / trigger gated). The cited vulnerable code path exists
in `sys/dev/disk/nvme/nvme_admin.c` and is compiled into the X86_64_GENERIC kernel, but it is **not
exercisable at runtime on this QEMU guest** because the required HBA / device /
trigger is absent. Confidence in the source bug itself: **certain**.

## Why it cannot be reproduced here (the gate)
Hard-gated: needs an NVMe controller. The guest has NO NVMe controller; nvme_admin_state_identify_ns never runs.

See `env.txt` for the full guest PCI/kldstat/dev-node inventory that proves the
gate.

## The bug is real in source (traced line-by-line)
Cited path:
- sys/dev/disk/nvme/nvme_admin.c:624
- sys/dev/disk/nvme/nvme_admin.c:630-634
- sys/dev/disk/nvme/nvme_admin.c:653
- sys/dev/disk/nvme/nvme_admin.c:671
- The vulnerable construct is present verbatim in the current master source
  (confirmed by direct read of the cited lines during verification).
- A defense-in-depth `fix.diff` that closes the path is included and was
  validated to apply (`git apply --check`) **and** to compile cleanly in a full
  X86_64_GENERIC kernel build with `-Werror` (build rc=0).

## Fix
Call nvme_put_request(req) on the failed-Identify-NS error path before continue, matching the success and nscary-full exit paths which do release the request.

The standalone git-apply-able diff is `fix.diff`.

## Reproduce
`./build.sh && ./run.sh` — both are no-ops on this guest by design (the gate
holds). Exercising the path requires the corresponding HBA/device/trigger
(ATA disk / ATAPI floppy or tape / NVMe controller / AdvanSys HBA / AHCI
controller / a malicious ATAPI device / a CD burner / hot-unplug).

## Status
status: not_reproduced  | reproduced: 0 | impact: none (HW-gated)
fix_status: not_testable (path cannot run on this guest; diff applies + compiles)