← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-89875

Last refreshed2026-10-19

Status: UPDATED  |  Advisory ID: CVE-2026-89875

Key Details

CVECVE-2026-89875
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-19
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-89875
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-89875
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.