CVE-2026-89867
Last modified
CVE-2026-89867 is a vulnerability of currently unknown severity. 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.
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
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a176ac5e701f1ba30843c0d7e0663a761bf9a61a, < 63d758d2f9dba836d5ae597d317cde522e817cf9; >= a176ac5e701f1ba30843c0d7e0663a761bf9a61a, < b694ba0a5526a69f78a6924982b1553154ccfd73 |
| Linux | Linux | 7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89867?
How severe is CVE-2026-89867?
How do I fix CVE-2026-89867?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-89861In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-89862In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89863In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-89864In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89865In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89866In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89868In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89869In the Linux kernel, the following vulnerability has been re…
- CVE-2026-8987Autel Maxi Charger Single firmware through V1.03.51 contains…8.8
- CVE-2026-89870In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89871In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89872In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-89867?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
