CVE-2026-68228: media: chips-media: wave5: Move src_buf Removal to finish_encode
In the Linux kernel, the following vulnerability has been resolved:
media: chips-media: wave5: Move srcbuf Removal to finishencode
During encoder processing, there is a case where the IRQ response could return the buffer back to userspace via v4l2m2mbufdone call. In this time, userspace could queue up this same buffer before startencode 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 WRITEONCE(prev->next, new) call in listadd.
When listdel is finally called, the loop is already made so nothing points back to ready queue list head and pointers are poisoned.
A buffer should not be marked as DONE before the buffer is removed from m2m ready queue. Move removal entirely to finishencode.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68228?
CVE-2026-68228 has a risk rating of 37.
How do I fix CVE-2026-68228?
To fix CVE-2026-68228, users should update their Linux kernel to the latest version that includes the patch.
What systems are affected by CVE-2026-68228?
CVE-2026-68228 affects systems running the Linux kernel with the specific media chip implementation.
What does CVE-2026-68228 impact in the Linux kernel?
CVE-2026-68228 impacts the encoder processing during buffer management.
Is there a workaround for CVE-2026-68228?
There is no known workaround for CVE-2026-68228; applying the kernel update is recommended.