https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 15:44:54 +0000 https://vulnerability.circl.lu/vuln/cve-2026-68228 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: chips-media: wave5: Move src_buf Removal to finish_encode</p> <p>During encoder processing, there is a case where the IRQ response could return the buffer back to userspace via v4l2_m2m_buf_done call. In this time, userspace could queue up this same buffer before start_encode removes the index from the ready queue. This would then lead to a case where the buffer in the ready queue could be a self loop due to the WRITE_ONCE(prev-&gt;next, new) call in __list_add.</p> <p>When __list_del is finally called, the loop is already made so nothing points back to ready queue list head and pointers are poisoned.</p> <p>A buffer should not be marked as DONE before the buffer is removed from m2m ready queue. Move removal entirely to finish_encode.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: chips-media: wave5: Move src_buf Removal to finish_encode</p> <p>During encoder processing, there is a case where the IRQ response could return the buffer back to userspace via v4l2_m2m_buf_done call. In this time, userspace could queue up this same buffer before start_encode removes the index from the ready queue. This would then lead to a case where the buffer in the ready queue could be a self loop due to the WRITE_ONCE(prev-&gt;next, new) call in __list_add.</p> <p>When __list_del is finally called, the loop is already made so nothing points back to ready queue list head and pointers are poisoned.</p> <p>A buffer should not be marked as DONE before the buffer is removed from m2m ready queue. Move removal entirely to finish_encode.</p> https://vulnerability.circl.lu/vuln/cve-2026-68228