# 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.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68228, DEBIAN-CVE-2026-68228, GHSA-rh59-gx8h-f2g3, UBUNTU-CVE-2026-68228

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68228 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-68228 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68228/ (Markdown: https://insights.sbomify.com/CVE-2026-68228/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68228
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68228
- OSV: https://osv.dev/vulnerability/CVE-2026-68228

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68228/
Summaries are generated and may contain mistakes; the official description above is the record.