Look up another CVE · open CVE-2026-93177 in the interactive tracker
CVE-2026-93177
drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup
Published 2026-09-17 (31 days ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-93177 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
vddInd, vddciInd and mvddInd from VBIOS-parsed tables index into vddc, vddci and vddmem lookup tables without bounds checks across nine sites. Return -EINVAL when any index is out of range.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/gpu/drm/amd/pm/powerplay/hwmgr/vega10_hwmgr.c
- What this is
- AMD POWERPLAY AND SWSMUMAINTAINERS section matched on drivers/gpu/drm/amd/pm/ · amd-gfx@lists.freedesktop.org · Supported
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid, bookworm · linux-6.12?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS
Signals
- Published
- 2026-09-17 (31 days ago)source
- CVSS
- 7.3 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.16%, higher than 4.7% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/gpu
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 4.12 | 5.10.270 | 206e478810d6 |
| 4.12 | 5.15.221 | 25dedc13ceb9 |
| 4.12 | 6.1.188 | ae25c92d91f2 |
| 4.12 | 6.6.157 | b349dcf061a6 |
| 4.12 | 6.12.110 | dfe89f1a0c7f |
| 4.12 | 6.18.52 | 46d27e56dbd6 |
| 4.12 | 7.2.6 | 06aef6dcc1d5 |
| 4.12 | 7.3 | 6fa33f594e46 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- Writing a crafted ATOM Vega10 POWERPLAYTABLE to sysfs pp_table (amdgpu_set_pp_table → pp_dpm_set_pp_table → amd_powerplay_reset → hwmgr_hw_init) makes vega10_pp_tables_initialize copy ucVddInd/ucVddciInd/ucVddMemInd into vddInd; vega10_hwmgr_backend_init then calls vega10_patch_voltage_dependency_tables_with_lookup_table. No network protocol carries those indices.
- AC:LAttack complexity, low
- The attacker fully controls ucVddInd in each ATOM_Vega10 dependency-table entry they write; get_socclk_voltage_dependency_table and get_mclk_voltage_dependency_table copy it verbatim into vddInd, and the unguarded entries[voltage_id].us_vdd load in vega10_patch_voltage_dependency_tables_with_lookup_table is deterministic with no race or victim state.
- PR:LPrivileges required, low
- amdgpu_set_pp_table and pp_dpm_set_pp_table perform no capable() check; the pp_table attribute is created as S_IRUGO|S_IWUSR, and AMD desktop/handheld udev rules commonly grant group write on pp_* nodes so unprivileged overclocking tools can use them (same attribute scored PR:L in CVE-2025-21780 and CVE-2026-74450).
- UI:NUser interaction, none
- The attacker writes the malformed POWERPLAYTABLE on their own pp_table sysfs node and amd_powerplay_reset runs in that store; no other user must mount a filesystem, plug in a GPU, or open a file.
- S:UScope, unchanged
- The OOB us_vdd load and later convert_to_vid SMC programming stay inside the host amdgpu powerplay heap and Vega10 SMU tables; they do not cross a KVM/IOMMU guest-host boundary (pp_table writes are rejected for SR-IOV VFs by amdgpu_dpm_is_pp_table_allowed).
- C:HConfidentiality impact, high
- voltage_id is a uint8_t taken from vddInd, so entries[voltage_id].us_vdd in vega10_patch_voltage_dependency_tables_with_lookup_table reads two bytes at an attacker-chosen offset of up to 255*sizeof(phm_ppt_v1_voltage_lookup_record) (~2.5KB) past a vddc_lookup_table that get_vddc_lookup_table allocated for only 8 entries (4 for vddci/vddmem).
- I:LIntegrity impact, low
- The OOB us_vdd is written only into in-bounds vddc/vddci/mvdd fields and later turned into SMC VIDs by convert_to_vid in vega10_populate_single_display_type and vega10_get_vdd_voltage_table, programming out-of-spec GPU rails. That is bounded power-management state corruption, not an arbitrary kernel write.
- A:HAvailability impact, high
- A ~2.5KB heap overread from the kmalloc-flex lookup table can oops or KASAN-panic, and garbage millivolts converted to VID and loaded into Vega10 PPTable_t DisplayClockTable via vega10_populate_single_display_type can hang or reset the GPU.