CVE-2026-93175

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
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.8Exploit: 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/amd/display: Fix dangling pointer in CRTC reset function

amdgpu_dm_crtc_reset_state() frees the old state before allocating a new one. If kzalloc() fails, the function returns without updating the state pointer, leaving a dangling pointer to already freed memory.

Fix this by allocating the new state first. On allocation failure, the old state remains untouched and the function safely returns.

Found by Linux Verification Center (linuxtesting.org) with SVACE.

[adjust for movement around current amd-staging-drm-next]

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/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
Severity78% × 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 (2)

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

drm/amd/display: Fix dangling pointer in CRTC reset function - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32bd68edbc6cbcfac0e4033b64f0bcadbf0efef5
generic

drm/amd/display: Fix dangling pointer in CRTC reset function - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0aeed866cb938943908c3ba46422128e49d2d080

Vendor Advisories for CVE-2026-93175(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 28× in last 7d / 74× 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.

  1. 2026-10-05 05:14 UTCEG score recompute
  2. 2026-10-05 05:14 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 18:00 UTCGHSA enrichment
  5. 2026-10-04 06:29 UTCGHSA enrichment
  6. 2026-10-03 19:16 UTCEG score recompute
  7. 2026-10-03 19:16 UTCGHSA enrichment
  8. 2026-10-03 08:04 UTCGHSA enrichment
  9. 2026-10-02 20:40 UTCEG score recompute
  10. 2026-10-02 20:40 UTCGHSA enrichment
  11. 2026-10-02 09:03 UTCGHSA enrichment
  12. 2026-10-01 21:45 UTCEG score recompute
  13. 2026-10-01 21:44 UTCGHSA enrichment
  14. 2026-10-01 19:51 UTCEPSS rescore
  15. 2026-10-01 10:27 UTCGHSA enrichment
  16. 2026-09-30 23:14 UTCEG score recompute
  17. 2026-09-30 23:14 UTCGHSA enrichment
  18. 2026-09-30 15:04 UTCEPSS rescore
  19. 2026-09-30 11:56 UTCGHSA enrichment
  20. 2026-09-30 00:43 UTCEG score recompute
  21. 2026-09-30 00:43 UTCGHSA enrichment
  22. 2026-09-29 13:26 UTCGHSA enrichment
  23. 2026-09-29 02:03 UTCEG score recompute
  24. 2026-09-29 02:03 UTCGHSA enrichment
  25. 2026-09-28 14:50 UTCEG score recompute
Show 49 more
  1. 2026-09-28 14:50 UTCGHSA enrichment
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 03:37 UTCGHSA enrichment
  5. 2026-09-27 16:22 UTCEG score recompute
  6. 2026-09-27 16:22 UTCGHSA enrichment
  7. 2026-09-27 13:49 UTCEPSS rescore
  8. 2026-09-27 05:09 UTCGHSA enrichment
  9. 2026-09-26 17:53 UTCEG score recompute
  10. 2026-09-26 17:53 UTCGHSA enrichment
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-26 06:35 UTCEG score recompute
  13. 2026-09-26 06:35 UTCGHSA enrichment
  14. 2026-09-25 19:19 UTCGHSA enrichment
  15. 2026-09-25 07:36 UTCGHSA enrichment
  16. 2026-09-24 20:23 UTCEG score recompute
  17. 2026-09-24 20:23 UTCGHSA enrichment
  18. 2026-09-24 14:04 UTCEPSS rescore
  19. 2026-09-24 09:10 UTCGHSA enrichment
  20. 2026-09-23 21:57 UTCEG score recompute
  21. 2026-09-23 21:57 UTCGHSA enrichment
  22. 2026-09-23 17:54 UTCEPSS rescore
  23. 2026-09-23 10:44 UTCGHSA enrichment
  24. 2026-09-22 23:30 UTCEG score recompute
  25. 2026-09-22 23:29 UTCGHSA enrichment
  26. 2026-09-22 16:01 UTCEPSS rescore
  27. 2026-09-22 12:12 UTCGHSA enrichment
  28. 2026-09-22 00:58 UTCEG score recompute
  29. 2026-09-22 00:58 UTCGHSA enrichment
  30. 2026-09-21 21:09 UTCEPSS rescore
  31. 2026-09-21 13:45 UTCGHSA enrichment
  32. 2026-09-21 02:32 UTCEG score recompute
  33. 2026-09-21 02:31 UTCGHSA enrichment
  34. 2026-09-20 20:16 UTCEPSS rescore
  35. 2026-09-20 15:18 UTCGHSA enrichment
  36. 2026-09-20 04:05 UTCGHSA enrichment
  37. 2026-09-19 16:52 UTCEG score recompute
  38. 2026-09-19 16:52 UTCGHSA enrichment
  39. 2026-09-19 05:39 UTCEG score recompute
  40. 2026-09-19 05:39 UTCGHSA enrichment
  41. 2026-09-18 19:28 UTCEPSS rescore
  42. 2026-09-18 18:26 UTCEG score recompute
  43. 2026-09-18 18:26 UTCGHSA enrichment
  44. 2026-09-18 18:00 UTCEG score recompute▲ 7.80
  45. 2026-09-18 18:00 UTCGHSA enrichment
  46. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  47. 2026-09-17 17:24 UTCNVD update
  48. 2026-09-17 16:20 UTCEG score recompute
  49. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93175?
CVE-2026-93175 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix dangling pointer in CRTC reset function amdgpudmcrtcresetstate() frees the old state before allocating a new one. If kzalloc() fails, the function returns without updating the state pointer, leaving a dangling…
When was CVE-2026-93175 disclosed?
CVE-2026-93175 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-93175 actively exploited?
CVE-2026-93175 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-93175?
CVE-2026-93175 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93175?
No fix for CVE-2026-93175 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-93175 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-93175

Explore →

Is Your Infrastructure Affected by CVE-2026-93175?

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

Book a Demo →Browse All CVEs