Answer in brief
CVE-2026-68228 records a Unknown severity 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.
A CVSS score is not reported in the current record. 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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| 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 |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Answer in brief
CVE-2026-68228 records a Unknown severity 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.
A CVSS score is not reported in the current record. 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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| 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 |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.