CVE-2026-93177: drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 06aef6dcc1d52da5112cbcde39c062e493247ab5, 206e478810d6af50b25d8da72e3af8d55a014365, 25dedc13ceb9b6109c79c92a726ca4ca017c9eaa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 06aef6dcc1d52da5112cbcde39c062e493247ab5, 206e478810d6af50b25d8da72e3af8d55a014365, 25dedc13ceb9b6109c79c92a726ca4ca017c9eaa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup 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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- f83a9991648bb4023a53104db699e99305890d51 and later · before 206e478810d6af50b25d8da72e3af8d55a014365affected · git
- f83a9991648bb4023a53104db699e99305890d51 and later · before 25dedc13ceb9b6109c79c92a726ca4ca017c9eaaaffected · git
- f83a9991648bb4023a53104db699e99305890d51 and later · before ae25c92d91f2cb90ede2b0eb0f58efa82ccc718baffected · git
- f83a9991648bb4023a53104db699e99305890d51 and later · before b349dcf061a6dc8c6cef9a10530331ef2ff66c72affected · git
- f83a9991648bb4023a53104db699e99305890d51 and later · before dfe89f1a0c7f40ef858b93881198f9728df956cfaffected · git
- f83a9991648bb4023a53104db699e99305890d51 and later · before 46d27e56dbd6345b9c7b62b67ec57407bf3bf29aaffected · git
- f83a9991648bb4023a53104db699e99305890d51 and later · before 06aef6dcc1d52da5112cbcde39c062e493247ab5affected · git
- f83a9991648bb4023a53104db699e99305890d51 and later · before 6fa33f594e46e775a94097f71b486d7b006b6917affected · git
- before 4.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93175Sep 17, 2026 · drm/amd/display: Fix dangling pointer in CRTC reset function31Monitor
- ← EarlierCVE-2026-93176Sep 17, 2026 · drm/amd/display: Fix dangling pointer in plane reset function28Monitor
- Later →CVE-2026-93178Sep 17, 2026 · drm/amdgpu/pm/powerplay: bounds-check voltage index in SMU7 lookup28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 06aef6dcc1d52da5112cbcde39c062e493247ab5 | Vendor (CNA) |
| Linux Linux | 206e478810d6af50b25d8da72e3af8d55a014365 | Vendor (CNA) |
| Linux Linux | 25dedc13ceb9b6109c79c92a726ca4ca017c9eaa | Vendor (CNA) |
| Linux Linux | 46d27e56dbd6345b9c7b62b67ec57407bf3bf29a | Vendor (CNA) |
| Linux Linux | 6fa33f594e46e775a94097f71b486d7b006b6917 | Vendor (CNA) |
| Linux Linux | ae25c92d91f2cb90ede2b0eb0f58efa82ccc718b | Vendor (CNA) |
| Linux Linux | b349dcf061a6dc8c6cef9a10530331ef2ff66c72 | Vendor (CNA) |
| Linux Linux | dfe89f1a0c7f40ef858b93881198f9728df956cf | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/206e478810d6af50b25d8da72e3af8d55a014365
- git.kernel.org/stable/c/25dedc13ceb9b6109c79c92a726ca4ca017c9eaa
- git.kernel.org/stable/c/46d27e56dbd6345b9c7b62b67ec57407bf3bf29a
- git.kernel.org/stable/c/6fa33f594e46e775a94097f71b486d7b006b6917
- git.kernel.org/stable/c/ae25c92d91f2cb90ede2b0eb0f58efa82ccc718b
- git.kernel.org/stable/c/b349dcf061a6dc8c6cef9a10530331ef2ff66c72
- git.kernel.org/stable/c/dfe89f1a0c7f40ef858b93881198f9728df956cf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.