media: chips-media: wave5: Move src_buf Removal to finish_encode (CVE-2026-68228) | HOL Guard CVE

High · CVSS 7.8CVE-2026-68228

media: chips-media: wave5: Move src_buf Removal to finish_encode

Answer in brief

CVE-2026-68228 records a High severity (CVSS 7.8) vulnerability in media: chips-media: wave5: Move src_buf Removal to finish_encode. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 10, 2026Updated Aug 17, 2026Source checked Sep 24, 2026First seen by HOL Aug 10, 2026Material review Aug 17, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.8
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=9707a6254a8a6b978bde811a44fe07d86c229d1c <1ee2b2b189ddc7b23c8eee1145de42b8bd19fb06 \|\| >=9707a6254a8a6b978bde811a44fe07d86c229d1c <f24ca8b53fe15db40957bdaa40c9aa68e1557bbe \|\| >=9707a6254a8a6b978bde811a44fe07d86c229d1c <d681227ce43bfd74b6eb69beecd9b0bec1fd8b48 \|\| >=9707a6254a8a6b978bde811a44fe07d86c229d1c <b20157147089a9c16a38c7810e2fe6f2df8e3277	1ee2b2b189ddc7b23c8eee1145de42b8bd19fb06, f24ca8b53fe15db40957bdaa40c9aa68e1557bbe, d681227ce43bfd74b6eb69beecd9b0bec1fd8b48, b20157147089a9c16a38c7810e2fe6f2df8e3277
Linux/Linuxgeneric	6.8	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 1ee2b2b189ddc7b23c8eee1145de42b8bd19fb06 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 10, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.