CVE-2026-89910

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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:

LoongArch: KVM: Fix uninitialized stack variable issue with dmsintc

Variable vector[] is declared on stack in function dmsintc_inject_irq() and sometimes it is used without initialized. Here fix this issue.

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
3rd
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 16, 2026

Last Modified

September 16, 2026

Advisory Details (2)

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

LoongArch: KVM: Fix uninitialized stack variable issue with dmsintc - kernel/git/stable/linux.git - Linux kernel stable tree

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

LoongArch: KVM: Fix uninitialized stack variable issue with dmsintc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81aa3a58b542ed88819115c80a17acd86eacb89d

Vendor Advisories for CVE-2026-89910(1)

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

Affected Packages

(1 across 1 ecosystem)
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 26× in last 7d / 78× 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 01:06 UTCEG score recompute
  2. 2026-10-05 01:06 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 12:58 UTCGHSA enrichment
  5. 2026-10-04 00:59 UTCEG score recompute
  6. 2026-10-04 00:59 UTCGHSA enrichment
  7. 2026-10-03 13:05 UTCGHSA enrichment
  8. 2026-10-03 01:10 UTCEG score recompute
  9. 2026-10-03 01:10 UTCGHSA enrichment
  10. 2026-10-02 13:16 UTCGHSA enrichment
  11. 2026-10-02 01:18 UTCEG score recompute
  12. 2026-10-02 01:18 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 13:24 UTCGHSA enrichment
  15. 2026-10-01 01:30 UTCEG score recompute
  16. 2026-10-01 01:30 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 13:37 UTCGHSA enrichment
  19. 2026-09-30 01:39 UTCEG score recompute
  20. 2026-09-30 01:39 UTCGHSA enrichment
  21. 2026-09-29 13:45 UTCGHSA enrichment
  22. 2026-09-29 01:41 UTCEG score recompute
  23. 2026-09-29 01:41 UTCGHSA enrichment
  24. 2026-09-28 13:52 UTCEPSS rescore
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 53 more
  1. 2026-09-28 13:47 UTCGHSA enrichment
  2. 2026-09-28 01:53 UTCGHSA enrichment
  3. 2026-09-27 13:58 UTCEG score recompute
  4. 2026-09-27 13:58 UTCGHSA enrichment
  5. 2026-09-27 13:49 UTCEPSS rescore
  6. 2026-09-27 02:00 UTCEG score recompute
  7. 2026-09-27 02:00 UTCGHSA enrichment
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-26 14:06 UTCGHSA enrichment
  10. 2026-09-26 02:03 UTCEG score recompute
  11. 2026-09-26 02:03 UTCGHSA enrichment
  12. 2026-09-25 14:09 UTCGHSA enrichment
  13. 2026-09-25 02:07 UTCGHSA enrichment
  14. 2026-09-24 14:13 UTCEG score recompute
  15. 2026-09-24 14:13 UTCGHSA enrichment
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-24 01:55 UTCEG score recompute
  18. 2026-09-24 01:55 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 14:01 UTCGHSA enrichment
  21. 2026-09-23 02:07 UTCEG score recompute
  22. 2026-09-23 02:07 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 14:12 UTCGHSA enrichment
  25. 2026-09-22 02:19 UTCEG score recompute
  26. 2026-09-22 02:19 UTCGHSA enrichment
  27. 2026-09-21 21:09 UTCEPSS rescore
  28. 2026-09-21 14:23 UTCGHSA enrichment
  29. 2026-09-21 02:26 UTCEG score recompute
  30. 2026-09-21 02:26 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEPSS rescore
  32. 2026-09-20 14:31 UTCGHSA enrichment
  33. 2026-09-20 02:37 UTCEG score recompute
  34. 2026-09-20 02:37 UTCGHSA enrichment
  35. 2026-09-19 14:43 UTCGHSA enrichment
  36. 2026-09-19 02:49 UTCEG score recompute
  37. 2026-09-19 02:49 UTCGHSA enrichment
  38. 2026-09-18 19:28 UTCEPSS rescore
  39. 2026-09-18 14:55 UTCGHSA enrichment
  40. 2026-09-18 03:01 UTCEG score recompute
  41. 2026-09-18 03:01 UTCGHSA enrichment
  42. 2026-09-17 19:32 UTCEPSS rescore
  43. 2026-09-17 15:07 UTCGHSA enrichment
  44. 2026-09-17 03:13 UTCEG score recompute
  45. 2026-09-17 03:13 UTCGHSA enrichment
  46. 2026-09-16 15:19 UTCEG score recompute
  47. 2026-09-16 15:19 UTCGHSA enrichment
  48. 2026-09-16 14:48 UTCEG score recompute▲ 7.30
  49. 2026-09-16 14:48 UTCGHSA enrichment
  50. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 7.3 · severity → HIGH
  51. 2026-09-16 11:21 UTCNVD update
  52. 2026-09-16 10:39 UTCEG score recompute
  53. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-89910?
CVE-2026-89910 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Fix uninitialized stack variable issue with dmsintc Variable vector[] is declared on stack in function dmsintcinjectirq() and sometimes it is used without initialized. Here fix this issue.
When was CVE-2026-89910 disclosed?
CVE-2026-89910 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89910 actively exploited?
CVE-2026-89910 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89910?
CVE-2026-89910 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-89910?
No fix for CVE-2026-89910 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-89910 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-89910

Explore →

Is Your Infrastructure Affected by CVE-2026-89910?

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