Look up another CVE · open CVE-2026-53380 in the interactive tracker
CVE-2026-53380
media: rzv2h-ivc: Fix concurrent buffer list access
Published 2026-07-19 (3 months 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-53380 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.0.9-1 | Update the kernel and reboot. Fixed in 7.0.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.0.9-1 | Update the kernel and reboot. Fixed in 7.0.9-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The list of buffers (`rzv2h_ivc::buffers.queue`) is protected by a spinlock (`rzv2h_ivc::buffers.lock`). However, in `rzv2h_ivc_transfer_buffer()`, which runs in a separate workqueue, the `list_del()` call is executed without holding the spinlock, which makes it possible for the list to be concurrently modified Fix that by removing a buffer from the list in the lock protected section. [assign ivc->buffers.curr in critical section as reported by Barnabas]
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/renesas/rzv2h-ivc/rzv2h-ivc-video.c
- What this is
- RENESAS RZ/V2H(P) INPUT VIDEO CONTROL BLOCK DRIVERMAINTAINERS section matched on drivers/media/platform/renesas/rzv2h-ivc/ · linux-media@vger.kernel.org · Maintained
Check it on the machine
grep -w CONFIG_VIDEO_RZV2H_IVC /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_RZV2H_IVC
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-07-19 (3 months 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.3% 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 |
|---|---|---|
| 6.19 | 7.0.9 | c746522bd326 |
| 6.19 | 7.1 | 72773ff1cdfa |
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 flaw is reached only through local V4L2 syscalls (open/ioctl/mmap) on the /dev/video* node registered by this platform driver; it is not triggered by remote network packets or physical bus insertion.
- AC:LAttack complexity, low
- An attacker controls both sides of the race by issuing concurrent VIDIOC_QBUF and VIDIOC_STREAMOFF/STREAMON calls from multiple threads while streaming, reliably interleaving with the workqueue handler that performs the unlocked list_del().
- PR:LPrivileges required, low
- Exploitation requires only a local account with access to the V4L2 video device node (typically membership in the video group or a dedicated vision-service account on RZ/V2H embedded deployments), not real root in the init namespace.
- UI:NUser interaction, none
- The attacker directly drives all required V4L2 ioctl operations to queue buffers and start/stop streaming; no independent victim action is needed.
- S:UScope, unchanged
- Successful exploitation corrupts kernel memory from a local userspace context to achieve kernel-level impact (crash, info leak, or privilege escalation), which remains within the same kernel security authority rather than crossing a VM or hypervisor boundary.
- C:HConfidentiality impact, high
- Unsynchronized list_del()/list manipulation on the buffer queue can corrupt kernel linked-list pointers and create use-after-free conditions when buffers are concurrently completed or returned, enabling arbitrary kernel memory reads.
- I:HIntegrity impact, high
- Corrupted list_head structures and concurrent assignment of ivc->buffers.curr outside the spinlock can yield exploitable heap corruption and arbitrary write primitives beyond a simple denial-of-service crash.
- A:HAvailability impact, high
- The race can cause kernel list corruption, use-after-free, and BUG/list debugging failures that result in kernel oops/panic when streaming buffers on affected RZ/V2H systems.