CVE-2026-53380: media: rzv2h-ivc: Fix concurrent buffer list access
In the Linux kernel, the following vulnerability has been resolved:
media: rzv2h-ivc: Fix concurrent buffer list access
The list of buffers (rzv2hivc::buffers.queue) is protected by a spinlock (rzv2hivc::buffers.lock). However, in rzv2hivctransferbuffer(), which runs in a separate workqueue, the listdel() 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]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
In the rzv2h-ivc code (media: rzv2h-ivc: Fix concurrent buffer list access), ensure the buffer list rzv2h_ivc::buffers.queue is protected by the spinlock (rzv2h_ivc::buffers.lock) by taking the lock for the list_del() path executed by rzv2h_ivc_transfer_buffer(), which runs in a separate workqueue. Also assign ivc->buffers.curr inside the same critical section.
Linux kernel (rzv2h-ivc) buffer list synchronization = assign ivc->buffers.curr within the rzv2h_ivc::buffers.lock critical section; execute list_del() only while holding the spinlock rzv2h_ivc::buffers.lock
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53380?
CVE-2026-53380 has a severity rating of high, with a CVSS score of 7.8.
How do I fix CVE-2026-53380?
To fix CVE-2026-53380, ensure you update to the latest version of the Linux kernel where the vulnerability has been addressed.
What impact does CVE-2026-53380 have on system security?
CVE-2026-53380 could allow unauthorized access to sensitive buffer data, potentially leading to information leakage and system instability.
What systems are affected by CVE-2026-53380?
CVE-2026-53380 affects the Linux kernel that implements the media rcv2h-ivc functionality.
Is CVE-2026-53380 actively being exploited?
There is no public indication that CVE-2026-53380 is actively being exploited, but it is recommended to apply patches promptly.