CVE-2026-89907

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.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: 8.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:

LoongArch: KVM: Validate MSI data before routing it to EIOINTC

pch_msi_set_irq() passes e->msi.data straight into eiointc_set_irq() as the irq number. The MSI data comes from userspace, that either via a KVM_IRQ_ROUTING_MSI entry set with KVM_SET_GSI_ROUTING (used by irqfd and KVM_IRQ_LINE) or directly via KVM_SIGNAL_MSI, and is never checked against EIOINTC_IRQS.

eiointc_set_irq() uses the value with __set_bit()/__clear_bit() on the 256-bit isr bitmap, eiointc_update_irq() then indexes sw_coremap[] and the per-cpu coreisr/sw_coreisr bitmaps with it. Therefore a data value >= 256 reads and writes memory past the end of those arrays, i.e. any process holding a VM fd can corrupt kernel memory beyond the allocation of loongarch_eiointc.

Reject MSI data that doesn't fit in the EIOINTC irq space. The DMSINTC path is unaffected as it decodes the vector from the address and masks it.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/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
Severity88% × 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 16, 2026

Last Modified

September 16, 2026

Advisory Details (2)

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

LoongArch: KVM: Validate MSI data before routing it to EIOINTC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/501514d6ebd2111c353a1296f25dbe22fbd64657
generic

LoongArch: KVM: Validate MSI data before routing it to EIOINTC - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83715a40a2d30d23719e0b25380ba82ff905195b

Vendor Advisories for CVE-2026-89907(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 27× 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 10:28 UTCEG score recompute
  2. 2026-10-05 10:28 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 22:01 UTCGHSA enrichment
  5. 2026-10-04 09:34 UTCGHSA enrichment
  6. 2026-10-03 21:07 UTCEG score recompute
  7. 2026-10-03 21:07 UTCGHSA enrichment
  8. 2026-10-03 08:40 UTCGHSA enrichment
  9. 2026-10-02 19:46 UTCEG score recompute
  10. 2026-10-02 19:46 UTCGHSA enrichment
  11. 2026-10-02 07:19 UTCEG score recompute
  12. 2026-10-02 07:19 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 18:53 UTCGHSA enrichment
  15. 2026-10-01 05:25 UTCGHSA enrichment
  16. 2026-09-30 16:58 UTCEG score recompute
  17. 2026-09-30 16:58 UTCGHSA enrichment
  18. 2026-09-30 15:04 UTCEPSS rescore
  19. 2026-09-30 03:33 UTCEG score recompute
  20. 2026-09-30 03:33 UTCGHSA enrichment
  21. 2026-09-29 15:06 UTCGHSA enrichment
  22. 2026-09-29 02:40 UTCEG score recompute
  23. 2026-09-29 02:40 UTCGHSA enrichment
  24. 2026-09-28 14:13 UTCEG score recompute
  25. 2026-09-28 14:13 UTCGHSA enrichment
Show 53 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 01:46 UTCEG score recompute
  4. 2026-09-28 01:46 UTCGHSA enrichment
  5. 2026-09-27 13:49 UTCEPSS rescore
  6. 2026-09-27 13:16 UTCGHSA enrichment
  7. 2026-09-27 00:49 UTCEG score recompute
  8. 2026-09-27 00:49 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 12:22 UTCEG score recompute
  11. 2026-09-26 12:22 UTCGHSA enrichment
  12. 2026-09-25 23:55 UTCGHSA enrichment
  13. 2026-09-25 11:28 UTCGHSA enrichment
  14. 2026-09-24 23:01 UTCEG score recompute
  15. 2026-09-24 23:01 UTCGHSA enrichment
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-24 10:11 UTCGHSA enrichment
  18. 2026-09-23 21:44 UTCEG score recompute
  19. 2026-09-23 21:44 UTCGHSA enrichment
  20. 2026-09-23 17:54 UTCEPSS rescore
  21. 2026-09-23 09:18 UTCGHSA enrichment
  22. 2026-09-22 20:51 UTCEG score recompute
  23. 2026-09-22 20:51 UTCGHSA enrichment
  24. 2026-09-22 16:01 UTCEPSS rescore
  25. 2026-09-22 08:25 UTCEG score recompute
  26. 2026-09-22 08:25 UTCGHSA enrichment
  27. 2026-09-21 21:09 UTCEPSS rescore
  28. 2026-09-21 19:58 UTCGHSA enrichment
  29. 2026-09-21 07:31 UTCEG score recompute
  30. 2026-09-21 07:31 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEPSS rescore
  32. 2026-09-20 19:04 UTCGHSA enrichment
  33. 2026-09-20 06:35 UTCGHSA enrichment
  34. 2026-09-19 18:02 UTCEG score recompute
  35. 2026-09-19 18:02 UTCGHSA enrichment
  36. 2026-09-19 05:34 UTCEG score recompute
  37. 2026-09-19 05:34 UTCGHSA enrichment
  38. 2026-09-18 19:28 UTCEPSS rescore
  39. 2026-09-18 17:08 UTCGHSA enrichment
  40. 2026-09-18 04:39 UTCEG score recompute
  41. 2026-09-18 04:39 UTCGHSA enrichment
  42. 2026-09-17 19:32 UTCEPSS rescore
  43. 2026-09-17 16:12 UTCGHSA enrichment
  44. 2026-09-17 03:46 UTCEG score recompute
  45. 2026-09-17 03:46 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▲ 8.80
  49. 2026-09-16 14:48 UTCGHSA enrichment
  50. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 8.8 · 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-89907?
CVE-2026-89907 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Validate MSI data before routing it to EIOINTC pchmsisetirq() passes e->msi.data straight into eiointcset_irq() as the irq number. The MSI data comes from userspace, that either via a KVMIRQROUTINGMSI entry set with…
When was CVE-2026-89907 disclosed?
CVE-2026-89907 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-89907 actively exploited?
CVE-2026-89907 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-89907?
CVE-2026-89907 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89907?
No fix for CVE-2026-89907 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-89907 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-89907

Explore →

Is Your Infrastructure Affected by CVE-2026-89907?

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

Book a Demo →Browse All CVEs