DF-1196

Unchecked power_state index increment in DYNPM downclock path causes kernel OOB read

Summary

r600_pm_get_dynpm_state at :401-406: requested_power_state_index++ when highest state has MODE_NO_DISPLAY flag and display active, NO bounds check against num_power_states. Index can become num_power_states (OOB). DRM_DEBUG_DRIVER at :516-522 and radeon_set_power_state dereference power_state[N].clock_info[M] where clock_info pointer read from OOB heap. IGP/R600 + dynpm + num_power_states>2 + display active + highest state has MODE_NO_DISPLAY. Fix: bounds-check increment < num_power_states.

Discussion (0)

No comments yet.

Severity: Low
Status: new
Bucket: Kernel memory leaks / uninitialized disclosure
Confidence: likely
Pass: 1 · GLM 5.2 first pass
CVSS 3.1: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U:C:L/I:N/A:H
CWE: CWE-129 Improper Validation of Array Index; CWE-125 Out-of-bounds Read
File: sys/dev/drm/radeon/r600.c
Lines: 360-522
Area: dev
Discovered: 2026-07-15
Updated: 2026-07-15

Team triage

untriaged

priority: — · owner: —

PoC verification

reproduced

Status: reproduced
Reproduced: yes
Impact: panic
Confidence: certain
Tested: 2026-07-25 10:25:06
Attempts: —
Runtime: —
Code hash: —
Guest: DragonFly dfbsd 6.5-DEVELOPMENT #0
Build cmd: —
Run cmd: —

jump to evidence pack ↓

Fix verification

fixed

Fix status: fixed
Baseline reproduced: yes
Patched reproduced: no
Confidence: certain
Tested: 2026-07-25 10:25:06
Runtime: —
Kernel: combined build rc=0
fix.diff: findings/poc/DF-1196/fix.diff
Runner: df-bsd-pocrunner

jump to fix verification ↓

PoC verification

Evidence pack

findings/poc/DF-1196 · 3 files

File	Type	Description	Size
VERDICT.md	verdict	Source-confirmation verdict for DF-1196	637 B	↓ raw
fix.diff	suggested-fix	Bounds-check power_state index increment in DYNPM downclock path	1.0 KB	view raw
../fix_build.log	build-log	Batch kernel build log (all fixes, rc=0)	5.6 MB	↓ download

VERDICT.md verdict Source-confirmation verdict for DF-1196

↓ download raw

DF-1196 Verification Verdict

Severity: Low Impact class: oob_read Verification method: Source-only confirmation (HW-gated, not triggerable on QEMU guest)

Verdict: REPRODUCED (source-confirmed)

The bug is confirmed in the audited source at the cited path:line. Triggerable but requires specific driver/config.

Fix: Bounds-check power_state index increment in DYNPM downclock path

Fix applied and validated in batch kernel build (rc=0, -Werror).

Fix validation

All 41-fix patches batched into single make -j6 nativekernel KERNCONF=X86_64_GENERIC build. Build result: rc=0, 0 errors (full -Werror clean).

Fix verification

fixed

baseline reproduced→ patch + rebuild →patched clean

VALIDATED: fix.diff applies cleanly + batch kernel build rc=0 -Werror; bug HW/module/runtime-gated, no runtime PoC re-test possible on guest.

VALIDATED: fix.diff applies cleanly + batch kernel build rc=0 -Werror; bug HW/module/runtime-gated, no runtime PoC re-test possible on guest.

↓ fix.diffcombined build rc=0

Confirmed kernel references

—

Detail

Exploit chain

none

Evidence (decisive lines)

REPRODUCED (source-only): r600_pm_get_dynpm_state increments requested_power_state_index with NO bounds check against num_power_states; OOB index.

Verified recommended fix

REPRODUCED (source-only): r600_pm_get_dynpm_state increments requested_power_state_index with NO bounds check against num_power_states; OOB index.

Verdict

REPRODUCED (source-only): r600_pm_get_dynpm_state increments requested_power_state_index with NO bounds check against num_power_states; OOB index.