CVE-2026-89867

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: 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: chips-media: wave5: Defer job_finish() only when a DEC_PIC was queued

Decoder instances sharing a VPU also share one v4l2_m2m job slot, released when the running context calls v4l2_m2m_job_finish(). While draining, device_run() defers job_finish() once EOS is sent (sent_eos), expecting a later finish_decode() (from a DEC_PIC completion IRQ) to release the slot.

But the m2m core checks job_ready() only when a job is queued, not when it is dispatched. A job queued while draining can run after finish_decode() has already moved the instance to STOP and sent EOS. device_run() then runs in STOP, issues no DEC_PIC, yet still skips job_finish() - so no IRQ, no finish_decode(), and the shared slot is leaked, stalling every instance. With several v4l2h264dec instances in parallel, GStreamer hangs at EOS.

Track whether the run actually queued a DEC_PIC (cmd_issued) and defer job_finish() only then. Otherwise finish the job immediately

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

References (2)

Vendor Advisories for CVE-2026-89867(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 8× in last 7d / 25× 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-04 23:22 UTCEPSS rescore
  2. 2026-10-03 05:07 UTCGHSA enrichment
  3. 2026-10-01 19:51 UTCEPSS rescore
  4. 2026-09-30 15:04 UTCEPSS rescore
  5. 2026-09-30 10:10 UTCEG score recompute
  6. 2026-09-30 10:10 UTCGHSA enrichment
  7. 2026-09-28 13:52 UTCEPSS rescore
  8. 2026-09-28 13:52 UTCEPSS rescore
  9. 2026-09-27 15:13 UTCGHSA enrichment
  10. 2026-09-27 13:49 UTCEPSS rescore
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-24 20:14 UTCGHSA enrichment
  13. 2026-09-24 14:04 UTCEPSS rescore
  14. 2026-09-23 17:54 UTCEPSS rescore
  15. 2026-09-22 16:01 UTCEPSS rescore
  16. 2026-09-22 01:17 UTCGHSA enrichment
  17. 2026-09-21 21:09 UTCEPSS rescore
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-19 06:20 UTCEG score recompute
  20. 2026-09-19 06:20 UTCGHSA enrichment
  21. 2026-09-18 19:28 UTCEPSS rescore
  22. 2026-09-17 19:32 UTCEPSS rescore
  23. 2026-09-16 11:21 UTCNVD update
  24. 2026-09-16 10:40 UTCEG score recompute
  25. 2026-09-16 10:36 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89867?
CVE-2026-89867 is a publicly disclosed vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Defer jobfinish() only when a DECPIC was queued Decoder instances sharing a VPU also share one v4l2_m2m job slot, released when the running context calls v4l2m2mjob_finish(). While draining, devicerun()…
When was CVE-2026-89867 disclosed?
CVE-2026-89867 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-89867 actively exploited?
CVE-2026-89867 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).
How do I remediate CVE-2026-89867?
No fix for CVE-2026-89867 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-89867 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-89867

Explore →

Is Your Infrastructure Affected by CVE-2026-89867?

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

Book a Demo →Browse All CVEs