CVE-2026-89801

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 — 4 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/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE

In nouveau_uvmm_bind_job_submit()'s OP_UNMAP_SPARSE arm, op->reg is set from nouveau_uvma_region_find(), which only looks the region up and takes no reference; a region's sole reference is its membership in uvmm->region_mt. Two failure paths leave op->reg set: the -ENOENT check when the region is busy, and the drm_gpuvm_sm_unmap_ops_create() failure. The sibling nouveau_uvmm_sm_unmap_prepare() failure just below clears op->reg; these two do not.

unwind_continue steps back one op, so the failing op is skipped by the unwind loop and its op->reg stays set. nouveau_uvmm_bind_job_cleanup() then enters its if (op->reg) branch and calls nouveau_uvma_region_remove() and nouveau_uvma_region_put() on it, dropping the tree's sole reference and freeing a region this job never created. The comment above the cleanup loop documents the broken invariant: op->reg must be NULL on submit failure.

This frees a live region on an unrelated failure, reachable single-job when drm_gpuvm_sm_unmap_ops_create() returns -ENOMEM; if another job owns the same region, its cleanup then removes and puts the freed region, a use-after-free. Clear op->reg on both failure paths.

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 (5)

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

drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88114e3a96582882e63b2f73aa7a5a9cf0d5073c
generic

drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4083d24c2636fde7b18076115af52820d203bc57
generic

drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24c25b182d17d1bdfde0088c96bdf6f93e8f46bc

Vendor Advisories for CVE-2026-89801(2)

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
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 37× in last 7d / 112× 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 112 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89801?
CVE-2026-89801 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/uvmm: fix premature region free on failed OPUNMAPSPARSE In nouveauuvmmbindjobsubmit()'s OPUNMAPSPARSE arm, op->reg is set from nouveauuvmaregion_find(), which only looks the region up and takes no reference; a region's…
When was CVE-2026-89801 disclosed?
CVE-2026-89801 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-89801 actively exploited?
CVE-2026-89801 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-89801?
CVE-2026-89801 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-89801?
No fix for CVE-2026-89801 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-89801 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-89801

Explore →

Is Your Infrastructure Affected by CVE-2026-89801?

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

Book a Demo →Browse All CVEs