CVE-2026-89823

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: fix race between partial drm_dev_register() failure and ioctl

If drm_dev_register() fails after registering a minor (e.g. render minor registered, primary minor fails), userspace could have opened the first minor and entered a drm_dev_enter() critical section. Since the unplugged flag was never set, the ioctl proceeds while the error path tears down device resources.

Fix this by introducing drm_dev_synchronize_unplug(), which sets the unplugged flag and waits for the SRCU barrier, ensuring all in-flight drm_dev_enter() critical sections complete before cleanup proceeds; call it on the error path of drm_dev_register().

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

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

drm: fix race between partial drm_dev_register() failure and ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm: fix race between partial drm_dev_register() failure and ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm: fix race between partial drm_dev_register() failure and ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79d09cfe90304ff4f195e47d569800f5e0f8b854
generic

drm: fix race between partial drm_dev_register() failure and ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6729990df9e70623bf53f855b521ae71ca9cb278
generic

drm: fix race between partial drm_dev_register() failure and ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d1215a72159d00001e08dee162e27718934bee9
generic

drm: fix race between partial drm_dev_register() failure and ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26d9162213952927cd59c0d94b7e0e992b347bec
generic

drm: fix race between partial drm_dev_register() failure and ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24d28d15c0f7f7d4a1c229f8730314f0f8758810
generic

drm: fix race between partial drm_dev_register() failure and ioctl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19dbfe4d586aecfed121cb3fa62281761d9d341f

Vendor Advisories for CVE-2026-89823(2)

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

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

Frequently asked(5)

What is CVE-2026-89823?
CVE-2026-89823 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: drm: fix race between partial drmdevregister() failure and ioctl If drmdevregister() fails after registering a minor (e.g. render minor registered, primary minor fails), userspace could have opened the first minor and entered a…
When was CVE-2026-89823 disclosed?
CVE-2026-89823 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-89823 actively exploited?
CVE-2026-89823 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-89823?
CVE-2026-89823 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-89823?
No fix for CVE-2026-89823 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-89823 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-89823

Explore →

Is Your Infrastructure Affected by CVE-2026-89823?

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