CVE-2026-89803

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:

drm/nouveau: unsubscribe the channel-kill event before the fence context

nouveau_channel_del() tears the fence context down first and only drops the channel-kill subscription later, in the middle of the nvif object teardown:

if (chan->fence) nouveau_fence(chan->cli->drm)->context_del(chan); ... nvif_object_dtor(&chan->vram); nvif_event_dtor(&chan->kill);

The subscribed handler is nouveau_channel_killed(), which calls nouveau_channel_kill() and from there nouveau_fence_context_kill() on chan->fence. A kill event delivered in that window takes fctx->lock and walks fctx->pending on a fence context that context_del() has already freed.

Nothing reaches this below Fermi today, because the subscription is gated on FERMI_CHANNEL_GPFIFO and nothing kills a channel there. On Fermi and newer the window is real but narrow, since a kill has to land exactly while the channel is being destroyed. That is reason enough on its own, which is why this carries a Fixes: tag. The last patch in this series subscribes Tesla channels as well; nothing kills those today, so it does not widen the exposure now, but it is the groundwork for a recovery path that would, and the ordering is better fixed before that lands than alongside it.

Drop the subscription before anything it depends on is torn down.

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
6th
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 (4)

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

drm/nouveau: unsubscribe the channel-kill event before the fence context - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/nouveau: unsubscribe the channel-kill event before the fence context - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/nouveau: unsubscribe the channel-kill event before the fence context - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/511585987d27d8cb668acebd399fc4deda23404c
generic

drm/nouveau: unsubscribe the channel-kill event before the fence context - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1fef7553dc628295c1208a4f2ac2094c62886e5d

Vendor Advisories for CVE-2026-89803(1)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
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 27× in last 7d / 79× 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:43 UTCEG score recompute
  2. 2026-10-05 01:43 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 13:48 UTCGHSA enrichment
  5. 2026-10-04 01:52 UTCEG score recompute
  6. 2026-10-04 01:52 UTCGHSA enrichment
  7. 2026-10-03 13:57 UTCGHSA enrichment
  8. 2026-10-03 01:50 UTCEG score recompute
  9. 2026-10-03 01:50 UTCGHSA enrichment
  10. 2026-10-02 13:54 UTCGHSA enrichment
  11. 2026-10-02 01:56 UTCEG score recompute
  12. 2026-10-02 01:56 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 14:00 UTCGHSA enrichment
  15. 2026-10-01 02:05 UTCEG score recompute
  16. 2026-10-01 02:05 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 14:07 UTCGHSA enrichment
  19. 2026-09-30 02:09 UTCEG score recompute
  20. 2026-09-30 02:09 UTCGHSA enrichment
  21. 2026-09-29 14:14 UTCGHSA enrichment
  22. 2026-09-29 02:19 UTCEG score recompute
  23. 2026-09-29 02:19 UTCGHSA enrichment
  24. 2026-09-28 14:21 UTCEG score recompute
  25. 2026-09-28 14:21 UTCGHSA enrichment
Show 54 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 02:26 UTCGHSA enrichment
  4. 2026-09-27 14:30 UTCEG score recompute
  5. 2026-09-27 14:30 UTCGHSA enrichment
  6. 2026-09-27 13:49 UTCEPSS rescore
  7. 2026-09-27 02:35 UTCEG score recompute
  8. 2026-09-27 02:35 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 14:39 UTCGHSA enrichment
  11. 2026-09-26 02:23 UTCEG score recompute
  12. 2026-09-26 02:23 UTCGHSA enrichment
  13. 2026-09-25 14:28 UTCGHSA enrichment
  14. 2026-09-25 02:24 UTCGHSA enrichment
  15. 2026-09-24 14:28 UTCEG score recompute
  16. 2026-09-24 14:28 UTCGHSA enrichment
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-24 02:32 UTCEG score recompute
  19. 2026-09-24 02:32 UTCGHSA enrichment
  20. 2026-09-23 17:54 UTCEPSS rescore
  21. 2026-09-23 14:37 UTCGHSA enrichment
  22. 2026-09-23 02:41 UTCEG score recompute
  23. 2026-09-23 02:41 UTCGHSA enrichment
  24. 2026-09-22 16:01 UTCEPSS rescore
  25. 2026-09-22 14:45 UTCGHSA enrichment
  26. 2026-09-22 02:50 UTCEG score recompute
  27. 2026-09-22 02:49 UTCGHSA enrichment
  28. 2026-09-21 21:09 UTCEPSS rescore
  29. 2026-09-21 14:54 UTCGHSA enrichment
  30. 2026-09-21 02:47 UTCEG score recompute
  31. 2026-09-21 02:47 UTCGHSA enrichment
  32. 2026-09-20 20:16 UTCEPSS rescore
  33. 2026-09-20 14:51 UTCGHSA enrichment
  34. 2026-09-20 02:56 UTCEG score recompute
  35. 2026-09-20 02:56 UTCGHSA enrichment
  36. 2026-09-19 14:58 UTCGHSA enrichment
  37. 2026-09-19 03:02 UTCEG score recompute
  38. 2026-09-19 03:02 UTCGHSA enrichment
  39. 2026-09-18 19:28 UTCEPSS rescore
  40. 2026-09-18 15:06 UTCGHSA enrichment
  41. 2026-09-18 03:11 UTCEG score recompute
  42. 2026-09-18 03:11 UTCGHSA enrichment
  43. 2026-09-17 19:32 UTCEPSS rescore
  44. 2026-09-17 15:16 UTCGHSA enrichment
  45. 2026-09-17 03:20 UTCEG score recompute
  46. 2026-09-17 03:19 UTCGHSA enrichment
  47. 2026-09-16 15:24 UTCEG score recompute
  48. 2026-09-16 15:24 UTCGHSA enrichment
  49. 2026-09-16 14:49 UTCEG score recompute▲ 7.80
  50. 2026-09-16 14:49 UTCGHSA enrichment
  51. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  52. 2026-09-16 11:21 UTCNVD update
  53. 2026-09-16 10:41 UTCEG score recompute
  54. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-89803?
CVE-2026-89803 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: unsubscribe the channel-kill event before the fence context nouveauchanneldel() tears the fence context down first and only drops the channel-kill subscription later, in the middle of the nvif object teardown: if…
When was CVE-2026-89803 disclosed?
CVE-2026-89803 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-89803 actively exploited?
CVE-2026-89803 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89803?
CVE-2026-89803 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-89803?
No fix for CVE-2026-89803 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-89803 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-89803

Explore →

Is Your Infrastructure Affected by CVE-2026-89803?

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