KernelScan.io

HIGH Introduced in 4.5

amdgpu VoltageIndex OOB

CVE-2026-93178

CVSS 7.1 / 10.0 NVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

KernelScan AI4.4MEDIUM

01

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/pm/powerplay: bounds-check voltage index in SMU7 lookup vddInd and vddcInd fields from VBIOS-parsed tables are used to index into voltage lookup tables without a bounds check. Return -EINVAL when any index is out of range.

02

Engine v0.6.0

Risk summary

AMD GPU systems using SMU7 powerplay (Tonga and similar) can hit an out-of-bounds read when VBIOS-parsed voltage tables contain invalid indices. A local administrator could trigger this during GPU power management initialization, causing a kernel oops or denial of service. The issue requires an AMD GPU with SMU7 powerplay support and a malformed VBIOS table.

Affecteddrivers/gpu/drm/amd/pm/powerplay/hwmgr/smu7_hwmgr.c (amdgpu powerplay)

Vulnerability analysis

The AMD GPU powerplay driver parses voltage dependency tables from the card's VBIOS and uses index fields from those tables to look up voltage values in separate lookup tables. When those index fields are out of range, the driver reads past the end of the lookup table array, causing an out-of-bounds memory read. The fix adds explicit bounds checks before each array access and returns an error if any index exceeds the lookup table size. This code path is reached during GPU power management initialization on AMD GPUs using the SMU7 powerplay framework, and the malformed data originates from the VBIOS firmware tables rather than from user-supplied input.

03

BranchIntroducedFixed inPatch commit
5.104.55.10.270d9ef085114d1
5.154.55.15.2216f08c001fa6e
6.14.56.1.188ce0d8e72836c
6.64.56.6.157745297208d31
6.124.56.12.110f925d317d84d
7.24.57.2.61664327ce797
mainline4.57.3-rc13a8a05477cda
6.184.56.18.528a3db9f593b6
cip/6.124.56.12.111-cip32f925d317d84d