# VERDICT -- DF-1368

## Verdict: INCONCLUSIVE at runtime; source bug CONFIRMED; fix COMPILE-VALIDATED

**Citations confirmed:**
  - sys/dev/drm/amd/powerplay/smumgr/vegam_smumgr.c:515
  - sys/dev/drm/amd/powerplay/smumgr/vegam_smumgr.c:1515
  - sys/dev/drm/amd/powerplay/smumgr/vegam_smumgr.c:1636
  - sys/dev/drm/amd/powerplay/smumgr/vegam_smumgr.c:1637
  - sys/dev/drm/amd/powerplay/smumgr/vegam_smumgr.c:1639

### Is the bug real? -- YES (source trace)

Three independent unclamped loops, all driven by VBIOS counts, writing fixed-size
arrays:
  * vegam_populate_cac_table :515 -- count from lookup_table->count writes
    BapmVddcVidLoSidd/HiSidd/HiSidd2[count], each [SMU75_MAX_LEVELS_VDDC=16].
  * vegam_populate_clock_stretcher_data_table :1515 -- sclk_table->count writes
    smc_state_table.Sclk_voltageOffset[i] (heap OOB, array [8]).
  * vegam_populate_avfs_parameters :1636 -- sclk_table->count writes
    AVFS_meanNsigma.Static_Voltage_Offset[i] and AVFS_SclkOffset.Sclk_Offset[i]
    (both stack-local structs of size [8] -> return-address corruption).
All counts come from VBIOS ucNumEntries unclamped.

### Can it be reproduced on this guest? -- NO (hardware-gated)

No AMD GPU in PCI list; amdgpu.ko not loaded.

The amdgpu driver is a loadable module only (NOT in `X86_64_GENERIC`), is not loaded, and cannot be `kldload`'d by an unprivileged user (kldload is root-only). Even loaded, it would not attach without the hardware.
Therefore the vulnerable code is unreachable at runtime here. Because the sinks are device-integrated parsers / DRM ioctls / DMA-supplied indices / hardware-dependent paths, no userspace harness on this guest can exercise them. This is the documented valid hard-blocker "unreachable at runtime + no feasible harness"; the bug is a real latent defect with the live trigger conditions noted above.

### No escalation chain (and why that is correct here)
There is no memory-corruption primitive to escalate on this guest: the corruption sinks live entirely inside the not-attached driver behind hardware that is absent. The escalation work the audit expects (slab groom -> victim -> uid0) presupposes a reachable write primitive; here there is none on the guest. The deliverable is therefore the confirmed root-cause + a compile-validated fix.

### Fix (fix.diff) -- authored and COMPILE-VALIDATED
Added `&& count < SMU75_MAX_LEVELS_VDDC` to the CAC loop and `&& i <
NUM_VFT_COLUMNS` (=8) to both the clock_stretcher and AVFS loops. (matches
finding proposal: clamp each loop to destination array size.)

The fix was applied to in-guest `/usr/src` (all hunks applied cleanly) and the
module was rebuilt with the kernel's `-Werror` flags: `cd /usr/src/sys/dev/drm/amdgpu && KERNCONF=X86_64_GENERIC SYSDIR=/usr/src/sys make -m /usr/src/share/mk` => rc=0 (see `build_fix.log`). No warnings or errors in the patched translation unit. The runtime before/after of the bug cannot be tested on this guest (no hardware), so fix_status is `not_testable` (diff applies + compiles; code path traced closed).

### Why not `not_reproduced` (false-positive)?
This is NOT a false positive. The cited `sys/` code is genuinely missing the guard / has the overflow / has the unclamped loop -- verified by reading the source. It is a real bug that is simply out of reach of this particular (driverless) QEMU guest.