Look up another CVE · open CVE-2026-89875 in the interactive tracker
CVE-2026-89875
media: ti: vpe: quiesce overflow recovery before freeing streams
Published 2026-09-16 (33 days ago) by the Linux kernel CNA. Subsystem drivers/media. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-89875 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/media/platform/ti/vpe/vip.c
- What this is
- TI VPE/CAL DRIVERSMAINTAINERS section matched on drivers/media/platform/ti/vpe/ · linux-media@vger.kernel.org · Maintained
Check it on the machine
grep -w CONFIG_VIDEO_TI_VIP /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code in 2 releases. The build rule could not be established for 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidn
- ?
- not established - no Makefile entry for the affected file
- n
- not enabled on any flavour - this release does not build the code
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switch
- CONFIG_VIDEO_TI_VIP
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-16 (33 days ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 5.4% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/media
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 7.0 | 7.2.5 | fd5b4a14c87b |
| 7.0 | 7.3 | aeaacc300144 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The bug is reached only through the TI VIP V4L2 capture node: a local process open()s /dev/videoX, STREAMONs to arm parser/list-complete IRQs and overflow recovery, then STREAMOFF or close() tears the stream down. It is not reachable from network packets or a remote peer.
- AC:LAttack complexity, low
- The attacker starts streaming (which generates list-complete IRQs and can queue recovery_work) and then STREAMOFF/close, racing the hardirq and an already-queued worker that the old teardown never drained. Both sides of the race are attacker-induced and retryable, so this UAF is Low complexity.
- PR:LPrivileges required, low
- Exploitation needs only an unprivileged local user who can open the VIP /dev/videoX node and issue V4L2 streaming ioctls. On DRA7/AM57 embedded, industrial, and automotive systems that is typically the video group or a camera app, not root or init-namespace capabilities.
- UI:NUser interaction, none
- The attacker performs open, STREAMON, and STREAMOFF/close themselves. No separate victim action such as mounting a filesystem or plugging in a device is required.
- S:UScope, unchanged
- The UAF corrupts host-kernel stream and VPDMA descriptor state used by the same kernel that serves the ioctl. That is standard kernel memory corruption/privilege escalation, not a VM, IOMMU, or sandbox boundary crossing.
- C:HConfidentiality impact, high
- This is a use-after-free of the VPDMA descriptor list (freed on last file release) and of the stream object (freed on unbind/remove). The IRQ and recovery worker then read those objects, which per CVSS kernel UAF guidance enables kernel memory disclosure.
- I:HIntegrity impact, high
- vip_overflow_recovery_work and the list-complete path write the freed descriptor buffer, rebuild DTDs, and resubmit VPDMA lists, giving a kernel write/DMA primitive suitable for control-flow hijack. UAF memory corruption is scored High integrity.
- A:HAvailability impact, high
- The same UAF and unlocked post_bufs/vidq walks from hardirq vs teardown oops or panic the kernel even when not fully exploited, so availability impact is High.