CVE-2026-89875

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:

media: ti: vpe: quiesce overflow recovery before freeing streams

The VIP overflow recovery worker is armed from the hardirq handler when a FIFO overflow is detected, and the list-complete path looks the stream up through the VPDMA list private pointer. Both keep touching stream, port and device state; the recovery worker also resets the parser and VPDMA, repopulates the descriptor list, and re-enables the per-list IRQs.

vip_stop_streaming() masks and clears the per-list IRQs, but it neither synchronizes the hardirq handler nor disables recovery_work. An overflow IRQ that has already queued recovery_work, or a list-complete IRQ in flight when the stream is torn down, can therefore still dereference the stream after its resources are released: the descriptor list is freed by vip_release_stream() on file release, and the stream itself by free_stream() on unbind/remove.

Drain the recovery worker and the IRQ handler at both teardown points through a shared vip_quiesce_stream() helper, before any stream-owned resource is released. disable_work_sync() cancels pending recovery_work, drains a running instance, and raises its disable depth, so a subsequent schedule_work() issued by a racing IRQ handler is rejected at the workqueue scheduler: recovery_work cannot be requeued after disable_work_sync() takes effect. The worker may still re-enable the per-list IRQs before disable_work_sync() returns; disable_irqs() then masks those sources and synchronize_irq() waits for any in-flight handler that still dereferences stream state. In vip_stop_streaming() the helper runs before the parser is stopped, since a worker drained by disable_work_sync() may re-enable the parser before exiting and would otherwise undo the stop. recovery_work is created disabled and enabled in vip_start_streaming() before IRQs, pairing the enable with the teardown disable across the streaming lifecycle.

This issue was found by an in-house static analysis tool and confirmed by manual code review.

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

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

media: ti: vpe: quiesce overflow recovery before freeing streams - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: ti: vpe: quiesce overflow recovery before freeing streams - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-89875(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 25× in last 7d / 78× 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 07:31 UTCEG score recompute
  2. 2026-10-05 07:31 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 20:24 UTCGHSA enrichment
  5. 2026-10-04 09:03 UTCGHSA enrichment
  6. 2026-10-03 21:56 UTCEG score recompute
  7. 2026-10-03 21:56 UTCGHSA enrichment
  8. 2026-10-03 10:40 UTCGHSA enrichment
  9. 2026-10-02 23:34 UTCEG score recompute
  10. 2026-10-02 23:34 UTCGHSA enrichment
  11. 2026-10-02 12:26 UTCGHSA enrichment
  12. 2026-10-02 00:23 UTCEG score recompute
  13. 2026-10-02 00:23 UTCGHSA enrichment
  14. 2026-10-01 19:51 UTCEPSS rescore
  15. 2026-10-01 13:17 UTCGHSA enrichment
  16. 2026-10-01 02:10 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEG score recompute
  18. 2026-09-30 15:04 UTCGHSA enrichment
  19. 2026-09-30 15:04 UTCEPSS rescore
  20. 2026-09-30 03:57 UTCGHSA enrichment
  21. 2026-09-29 16:51 UTCEG score recompute
  22. 2026-09-29 16:51 UTCGHSA enrichment
  23. 2026-09-29 05:32 UTCEG score recompute
  24. 2026-09-29 05:32 UTCGHSA enrichment
  25. 2026-09-28 18:25 UTCGHSA enrichment
Show 53 more
  1. 2026-09-28 06:08 UTCGHSA enrichment
  2. 2026-09-27 19:02 UTCEG score recompute
  3. 2026-09-27 19:02 UTCGHSA enrichment
  4. 2026-09-27 13:49 UTCEPSS rescore
  5. 2026-09-27 07:56 UTCGHSA enrichment
  6. 2026-09-26 20:49 UTCEG score recompute
  7. 2026-09-26 20:49 UTCGHSA enrichment
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-26 09:42 UTCEG score recompute
  10. 2026-09-26 09:42 UTCGHSA enrichment
  11. 2026-09-25 22:34 UTCGHSA enrichment
  12. 2026-09-25 10:50 UTCGHSA enrichment
  13. 2026-09-24 23:22 UTCEG score recompute
  14. 2026-09-24 23:22 UTCGHSA enrichment
  15. 2026-09-24 14:04 UTCEPSS rescore
  16. 2026-09-24 12:16 UTCGHSA enrichment
  17. 2026-09-24 01:09 UTCEG score recompute
  18. 2026-09-24 01:09 UTCGHSA enrichment
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-23 14:02 UTCGHSA enrichment
  21. 2026-09-23 02:56 UTCEG score recompute
  22. 2026-09-23 02:56 UTCGHSA enrichment
  23. 2026-09-22 16:01 UTCEPSS rescore
  24. 2026-09-22 15:49 UTCGHSA enrichment
  25. 2026-09-22 04:43 UTCEG score recompute
  26. 2026-09-22 04:43 UTCGHSA enrichment
  27. 2026-09-21 21:09 UTCEPSS rescore
  28. 2026-09-21 17:36 UTCGHSA enrichment
  29. 2026-09-21 06:30 UTCEG score recompute
  30. 2026-09-21 06:30 UTCGHSA enrichment
  31. 2026-09-20 20:16 UTCEPSS rescore
  32. 2026-09-20 19:23 UTCGHSA enrichment
  33. 2026-09-20 08:17 UTCGHSA enrichment
  34. 2026-09-19 21:10 UTCGHSA enrichment
  35. 2026-09-19 10:02 UTCGHSA enrichment
  36. 2026-09-18 22:56 UTCEG score recompute
  37. 2026-09-18 22:56 UTCGHSA enrichment
  38. 2026-09-18 19:28 UTCEPSS rescore
  39. 2026-09-18 11:50 UTCGHSA enrichment
  40. 2026-09-18 00:43 UTCEG score recompute
  41. 2026-09-18 00:43 UTCGHSA enrichment
  42. 2026-09-17 19:32 UTCEPSS rescore
  43. 2026-09-17 13:36 UTCGHSA enrichment
  44. 2026-09-17 02:29 UTCEG score recompute
  45. 2026-09-17 02:28 UTCGHSA enrichment
  46. 2026-09-16 15:19 UTCEG score recompute
  47. 2026-09-16 15:19 UTCGHSA enrichment
  48. 2026-09-16 14:48 UTCEG score recompute▲ 7.80
  49. 2026-09-16 14:48 UTCGHSA enrichment
  50. 2026-09-16 14:45 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  51. 2026-09-16 11:21 UTCNVD update
  52. 2026-09-16 10:40 UTCEG score recompute
  53. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-89875?
CVE-2026-89875 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: media: ti: vpe: quiesce overflow recovery before freeing streams The VIP overflow recovery worker is armed from the hardirq handler when a FIFO overflow is detected, and the list-complete path looks the stream up through the VPDMA…
When was CVE-2026-89875 disclosed?
CVE-2026-89875 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-89875 actively exploited?
CVE-2026-89875 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-89875?
CVE-2026-89875 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-89875?
No fix for CVE-2026-89875 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-89875 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-89875

Explore →

Is Your Infrastructure Affected by CVE-2026-89875?

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