CVE-2026-89919

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. 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:

KVM: s390: keyop: use mmu_lock to read gmap->asce

Every other dat_* consumer in this file (kvm_s390_get_skeys, set_skeys, get_cmma_bits, set_cmma_bits, MEM_CLR_CMMA, kvm_s390_fixup_prefix, kvm_test_age_gfn, kvm_age_gfn) reads kvm->arch.gmap->asce *inside* the mmu_lock read-side. keyop is the only outlier.

gmap->asce is mutated under write_lock(mmu_lock) by gmap_set_limit() and keyop might use a stale asce value for walking as KVM_S390_KEYOP and KVM_S390_VM_MEM_LIMIT_SIZE can run concurrently. This can result in memory corruption.

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

Last Modified

September 16, 2026

Advisory Details (2)

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

KVM: s390: keyop: use mmu_lock to read gmap->asce - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: s390: keyop: use mmu_lock to read gmap->asce - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ae452b990e0544425f77045351c56e77158858e7

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

Frequently asked(5)

What is CVE-2026-89919?
CVE-2026-89919 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: KVM: s390: keyop: use mmu_lock to read gmap->asce Every other dat* consumer in this file (kvms390getskeys, setskeys, getcmmabits, setcmmabits, MEMCLR_CMMA, kvms390fixupprefix, kvmtestagegfn, kvmagegfn) reads kvm->arch.gmap->asce…
When was CVE-2026-89919 disclosed?
CVE-2026-89919 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-89919 actively exploited?
CVE-2026-89919 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-89919?
CVE-2026-89919 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-89919?
No fix for CVE-2026-89919 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-89919 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-89919

Explore →

Is Your Infrastructure Affected by CVE-2026-89919?

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

Book a Demo →Browse All CVEs