CVE-2026-89806

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.4EG
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.4Exploit: 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/sysfb: ofdrm: Fix integer overflow in fb_size calculation

The framebuffer size calculation fb_size = linebytes * height can overflow when both values are large (e.g., 46341 * 46341 > INT_MAX). Since linebytes and height are both int types, the multiplication is performed as int * int, which results in undefined behavior on overflow.

Use check_mul_overflow() to detect and prevent this overflow, consistent with the approach used in simpledrm.c and corebootdrm.c.

CVSS v3
8.4
EG Score
8.4HIGHhigh confidence
EG Risk
42
EG Risk 42/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
Severity84% × 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
8th
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

October 3, 2026

Advisory Details (3)

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

drm/sysfb: ofdrm: Fix integer overflow in fb_size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/sysfb: ofdrm: Fix integer overflow in fb_size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/sysfb: ofdrm: Fix integer overflow in fb_size calculation - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-89806(2)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
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 / 119× 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 119 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89806?
CVE-2026-89806 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/sysfb: ofdrm: Fix integer overflow in fb_size calculation The framebuffer size calculation fb_size = linebytes * height can overflow when both values are large (e.g., 46341 * 46341 > INT_MAX). Since linebytes and height are…
When was CVE-2026-89806 disclosed?
CVE-2026-89806 was first published on September 16, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89806 actively exploited?
CVE-2026-89806 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89806?
CVE-2026-89806 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89806?
No fix for CVE-2026-89806 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-89806 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-89806

Explore →

Is Your Infrastructure Affected by CVE-2026-89806?

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