# DF-1388 -- Integer overflow in find_section BDB block-size check

**File:** `sys/dev/drm/i915/intel_bios.c:83`
**Class:** memory corruption (heap OOB / OOB write / OOB read)

## Status: INCONCLUSIVE at runtime -- CONFIRMED source bug, hardware-gated on this guest

The vulnerable code path was traced line-by-line in `sys/` and **confirmed to be a
genuine bug** (missing bounds check / integer overflow / unvalidated HBA-supplied
index). However it is **not exercisable on the DragonFly audit guest** because the
guest has no i915 hardware:

- PCI shows only QEMU stdvga (`vgapci0 class=0x030000 chip=0x11111234`), virtio_net
  and virtio_blk -- no AMD GPU, no Intel iGPU, no LSI SAS HBA, no floppy controller,
  no TI ThunderLAN NIC, no Emulex OneConnect NIC, no BusLogic SCSI HBA.
- The i915 driver (whether a loadable .ko or compiled-in) never attaches.
- `/dev/fd0`, `/dev/dri`, `/dev/dsp*` do not exist on this guest.

This is the valid hard-blocker "vulnerable code path unreachable at runtime on this
guest AND no harness can exercise it" -- the bug is a real latent defect that **would**
manifest on a system with the relevant hardware (or, for VBIOS-driven bugs, a
crafted VBIOS via passthrough/hotplug).

## Mechanism (confirmed by source trace)

find_section() does `if (index + current_size > total) return NULL;`. `index` is
    `int`, `current_size` is `u32`. In C's normal arithmetic, `int + u32` promotes
the int to u32 and the sum wraps mod 2^32. With current_size=0xFFFFFFFF and
index=6, the sum wraps to 5, which is < total => block accepted even though it
extends past the BDB. find_panel_sequence_block :864 then re-reads the size as
`total` and parses past the BDB. MIPI v3 _get_blocksize is the only path that
returns u32; it returns the value from `*((const u32 *)(block_base + 4))` which
is attacker-VBT-controlled. Reached via GPU ROM or OpRegion.

## Live trigger conditions
Requires the i915 hardware (and the driver loaded). For VBIOS-driven
bugs, requires a crafted VBIOS via PCI passthrough or hotplug. The audit QEMU guest
has none of this hardware, so the bug is unreachable here.

## Fix
A standalone, `git apply`-able fix is in `fix.diff`. **Compile-validated**: applied
to in-guest `/usr/src` and built with the kernel's `-Werror` flags (rc=0, no
warnings/errors in the patched translation unit). See `build_fix.log`.

Rewrote overflow-safe: `if (current_size > total - index) return NULL;`.
(matches finding proposal exactly.)

## Reproduce / validate
```
# 1. Confirm the bug site (read-only source trace):
grep -n ... sys/dev/drm/i915/intel_bios.c

# 2. Compile-validate the fix on the audit guest:
scp -F dfbsd-qemu/config findings/poc/DF-1388/fix.diff dfbsd:/root/DF-1388.fix.diff
./dfbsd-qemu/vm.sh run_root 'cd /usr/src && patch -p1 --forward < /root/DF-1388.fix.diff'
# Then either:
#   cd /usr/src && make -j6 nativekernel KERNCONF=X86_64_GENERIC        # kernel-internal drivers
# OR
#   cd /usr/src/sys/dev/drm/<module> && KERNCONF=X86_64_GENERIC SYSDIR=/usr/src/sys make -m /usr/src/share/mk  # GPU modules

# 3. (requires real hardware) Exercise the bug: attach the HW and trigger.
```