# CVE-2026-89867: media: chips-media: wave5: Defer job_finish() only when a DEC_PIC was queued

> A logic error in the Wave5 video decoder driver causes a resource leak, leading to a denial of service when multiple decoder instances are used.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-89867, GHSA-vhv2-9p64-c86q, UBUNTU-CVE-2026-89867

## What is CVE-2026-89867?

CVE-2026-89867 is a denial of service vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

## Which versions are affected by CVE-2026-89867?


## How do I fix CVE-2026-89867?

Apply the vendor's patch.

## Is CVE-2026-89867 being exploited?

There is no known exploitation of CVE-2026-89867 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89867 and fix it if it is affected.

What it is: CVE-2026-89867 is a denial of service vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89867 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89867/ (Markdown: https://insights.sbomify.com/CVE-2026-89867/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89867
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89867
- OSV: https://osv.dev/vulnerability/CVE-2026-89867

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89867/
Summaries are generated and may contain mistakes; the official description above is the record.