CVE-2026-68228 media: chips-media: wave5: Move src_buf Removal to finish_encode
A race condition in the Linux kernel wave5 media driver can cause a self-loop in the buffer queue, leading to pointer corruption and potential denial of service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-68228?
CVE-2026-68228 is a high-severity vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
In the Linux kernel, the following vulnerability has been resolved:
media: chips-media: wave5: Move src_buf Removal to finish_encode
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->next, new) call in __list_add.
When __list_del 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 finish_encode.
Which versions are affected by CVE-2026-68228?
How do I fix CVE-2026-68228?
Apply the vendor's patch.
Is CVE-2026-68228 being exploited?
There is no known exploitation of CVE-2026-68228 in the wild and no public exploit code.
Sources
Also known as BELL-CVE-2026-68228, DEBIAN-CVE-2026-68228, GHSA-rh59-gx8h-f2g3, UBUNTU-CVE-2026-68228.