# CVE-2026-93178: drm/amdgpu/pm/powerplay: bounds-check voltage index in SMU7 lookup

> Missing bounds checks in the AMD GPU powerplay driver allow out-of-bounds reads from voltage lookup tables, potentially causing information disclosure or system crashes.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102029, BELL-CVE-2026-93178, DEBIAN-CVE-2026-93178, GHSA-fw9r-626q-5x54, UBUNTU-CVE-2026-93178

## What is CVE-2026-93178?

CVE-2026-93178 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-93178?


## How do I fix CVE-2026-93178?

Apply the vendor's patch.

## Is CVE-2026-93178 being exploited?

There is no known exploitation of CVE-2026-93178 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93178 and fix it if it is affected.

What it is: CVE-2026-93178 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93178 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93178/ (Markdown: https://insights.sbomify.com/CVE-2026-93178/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93178
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93178
- OSV: https://osv.dev/vulnerability/CVE-2026-93178

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93178/
Summaries are generated and may contain mistakes; the official description above is the record.