CVE-2026-89887

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:

media: i2c: ov7740: fix use-after-destroy in remove

The ov7740_remove() function had a severe teardown order bug where it destroyed the driver's mutex before freeing the V4L2 control handler which relies on that mutex, leading to a use-after-destroy kernel panic. Furthermore, the driver explicitly called v4l2_ctrl_handler_free() and mutex_destroy() sequentially, but then called ov7740_free_controls() which invokes both of them a second time, resulting in a double-free.

This patch fixes the issue by unregistering the subdevice first, and relying exclusively on ov7740_free_controls() to safely tear down the mutex and control handler in the correct order.

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

media: i2c: ov7740: fix use-after-destroy in remove - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: i2c: ov7740: fix use-after-destroy in remove - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e4693436c7dcf8584002500ce4b434b79bbf9ed
generic

media: i2c: ov7740: fix use-after-destroy in remove - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a02ee6c1c4e88f3a0442bd60d3c77db9a30db5e
generic

media: i2c: ov7740: fix use-after-destroy in remove - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81e9765878d3ac8ad18e3a683332b5d6bc3a0e33
generic

media: i2c: ov7740: fix use-after-destroy in remove - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7512838a19af0a284a58435292243fad21e57ff1
generic

media: i2c: ov7740: fix use-after-destroy in remove - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d1b3dea5a44124bab6c14a2d71b977dabed54e7
generic

media: i2c: ov7740: fix use-after-destroy in remove - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25e2505866c577db2661e4d431f0907c6ec9a3b4
generic

media: i2c: ov7740: fix use-after-destroy in remove - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09453b467990e8ef8fe09f45a685f9a625248d33

Vendor Advisories for CVE-2026-89887(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 38× in last 7d / 108× 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 108 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-89887?
CVE-2026-89887 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: media: i2c: ov7740: fix use-after-destroy in remove The ov7740_remove() function had a severe teardown order bug where it destroyed the driver's mutex before freeing the V4L2 control handler which relies on that mutex, leading to a…
When was CVE-2026-89887 disclosed?
CVE-2026-89887 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-89887 actively exploited?
CVE-2026-89887 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-89887?
CVE-2026-89887 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-89887?
No fix for CVE-2026-89887 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-89887 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-89887

Explore →

Is Your Infrastructure Affected by CVE-2026-89887?

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