CVE-2026-93177

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.3Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
7.3
EG Score
7.3HIGHhigh confidence
EG Risk
37
EG Risk 37/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (8)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dfe89f1a0c7f40ef858b93881198f9728df956cf
generic

drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b349dcf061a6dc8c6cef9a10530331ef2ff66c72
generic

drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ae25c92d91f2cb90ede2b0eb0f58efa82ccc718b
generic

drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fa33f594e46e775a94097f71b486d7b006b6917
generic

drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46d27e56dbd6345b9c7b62b67ec57407bf3bf29a
generic

drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25dedc13ceb9b6109c79c92a726ca4ca017c9eaa
generic

drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/206e478810d6af50b25d8da72e3af8d55a014365
generic

drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06aef6dcc1d52da5112cbcde39c062e493247ab5

Vendor Advisories for CVE-2026-93177(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 43× in last 7d / 110× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 110 total refreshes for this CVE.

  1. 2026-10-05 08:28 UTCEG score recompute
  2. 2026-10-05 08:28 UTCVendor advisory
  3. 2026-10-05 08:28 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 21:26 UTCVendor advisory
  6. 2026-10-04 21:26 UTCGHSA enrichment
  7. 2026-10-04 10:24 UTCVendor advisory
  8. 2026-10-04 10:24 UTCGHSA enrichment
  9. 2026-10-03 23:21 UTCEG score recompute
  10. 2026-10-03 23:21 UTCVendor advisory
  11. 2026-10-03 23:21 UTCGHSA enrichment
  12. 2026-10-03 12:18 UTCVendor advisory
  13. 2026-10-03 12:18 UTCGHSA enrichment
  14. 2026-10-03 01:16 UTCEG score recompute
  15. 2026-10-03 01:16 UTCVendor advisory
  16. 2026-10-03 01:15 UTCGHSA enrichment
  17. 2026-10-02 14:13 UTCVendor advisory
  18. 2026-10-02 14:13 UTCGHSA enrichment
  19. 2026-10-02 03:10 UTCEG score recompute
  20. 2026-10-02 03:10 UTCVendor advisory
  21. 2026-10-02 03:10 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 16:06 UTCVendor advisory
  24. 2026-10-01 16:06 UTCGHSA enrichment
  25. 2026-10-01 05:04 UTCVendor advisory
Show 75 more
  1. 2026-10-01 05:04 UTCGHSA enrichment
  2. 2026-09-30 18:03 UTCEG score recompute
  3. 2026-09-30 18:03 UTCVendor advisory
  4. 2026-09-30 18:03 UTCGHSA enrichment
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-30 06:45 UTCVendor advisory
  7. 2026-09-30 06:45 UTCGHSA enrichment
  8. 2026-09-29 19:42 UTCEG score recompute
  9. 2026-09-29 19:42 UTCVendor advisory
  10. 2026-09-29 19:42 UTCGHSA enrichment
  11. 2026-09-29 08:31 UTCEG score recompute
  12. 2026-09-29 08:31 UTCVendor advisory
  13. 2026-09-29 08:31 UTCGHSA enrichment
  14. 2026-09-28 21:28 UTCEG score recompute
  15. 2026-09-28 21:28 UTCVendor advisory
  16. 2026-09-28 21:28 UTCGHSA enrichment
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 10:26 UTCVendor advisory
  20. 2026-09-28 10:26 UTCGHSA enrichment
  21. 2026-09-27 23:24 UTCEG score recompute
  22. 2026-09-27 23:24 UTCVendor advisory
  23. 2026-09-27 23:24 UTCGHSA enrichment
  24. 2026-09-27 13:49 UTCEPSS rescore
  25. 2026-09-27 12:22 UTCVendor advisory
  26. 2026-09-27 12:22 UTCGHSA enrichment
  27. 2026-09-27 01:20 UTCEG score recompute
  28. 2026-09-27 01:20 UTCVendor advisory
  29. 2026-09-27 01:19 UTCGHSA enrichment
  30. 2026-09-26 15:59 UTCEPSS rescore
  31. 2026-09-26 14:14 UTCVendor advisory
  32. 2026-09-26 14:14 UTCGHSA enrichment
  33. 2026-09-26 03:10 UTCEG score recompute
  34. 2026-09-26 03:10 UTCVendor advisory
  35. 2026-09-26 03:10 UTCGHSA enrichment
  36. 2026-09-25 16:07 UTCVendor advisory
  37. 2026-09-25 16:07 UTCGHSA enrichment
  38. 2026-09-25 05:05 UTCVendor advisory
  39. 2026-09-25 05:05 UTCGHSA enrichment
  40. 2026-09-24 18:03 UTCEG score recompute
  41. 2026-09-24 18:03 UTCVendor advisory
  42. 2026-09-24 18:03 UTCGHSA enrichment
  43. 2026-09-24 14:04 UTCEPSS rescore
  44. 2026-09-24 06:58 UTCVendor advisory
  45. 2026-09-24 06:58 UTCGHSA enrichment
  46. 2026-09-23 19:56 UTCEG score recompute
  47. 2026-09-23 19:56 UTCVendor advisory
  48. 2026-09-23 19:56 UTCGHSA enrichment
  49. 2026-09-23 17:54 UTCEPSS rescore
  50. 2026-09-23 08:54 UTCVendor advisory
  51. 2026-09-23 08:54 UTCGHSA enrichment
  52. 2026-09-22 21:52 UTCEG score recompute
  53. 2026-09-22 21:52 UTCVendor advisory
  54. 2026-09-22 21:52 UTCGHSA enrichment
  55. 2026-09-22 16:01 UTCEPSS rescore
  56. 2026-09-22 10:49 UTCVendor advisory
  57. 2026-09-22 10:49 UTCGHSA enrichment
  58. 2026-09-21 23:48 UTCEG score recompute
  59. 2026-09-21 23:48 UTCVendor advisory
  60. 2026-09-21 23:47 UTCGHSA enrichment
  61. 2026-09-21 21:09 UTCEPSS rescore
  62. 2026-09-21 12:45 UTCVendor advisory
  63. 2026-09-21 12:45 UTCGHSA enrichment
  64. 2026-09-21 01:43 UTCEG score recompute
  65. 2026-09-21 01:43 UTCVendor advisory
  66. 2026-09-21 01:43 UTCGHSA enrichment
  67. 2026-09-20 20:16 UTCEPSS rescore
  68. 2026-09-20 14:40 UTCVendor advisory
  69. 2026-09-20 14:40 UTCGHSA enrichment
  70. 2026-09-20 03:33 UTCVendor advisory
  71. 2026-09-20 03:33 UTCGHSA enrichment
  72. 2026-09-19 16:31 UTCEG score recompute
  73. 2026-09-19 16:31 UTCVendor advisory
  74. 2026-09-19 16:31 UTCGHSA enrichment
  75. 2026-09-19 05:29 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-93177?
CVE-2026-93177 is a high vulnerability published on September 17, 2026. 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…
When was CVE-2026-93177 disclosed?
CVE-2026-93177 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93177 actively exploited?
CVE-2026-93177 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93177?
CVE-2026-93177 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93177?
No fix for CVE-2026-93177 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93177 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-93177

Explore →

Is Your Infrastructure Affected by CVE-2026-93177?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.