CVE-2026-68211: media: stm32-dcmipp: Return queued buffers on start_streaming() failure
In the Linux kernel, the following vulnerability has been resolved:
media: stm32-dcmipp: Return queued buffers on startstreaming() failure
The vb2 framework hands buffers to the driver via bufqueue() before calling startstreaming(). If startstreaming() returns an error without first returning those buffers via vb2bufferdone(), vb2startstreaming() fires WARNON(ownedbydrvcount) and the queued buffers leak.
dcmippbytecapstartstreaming() returned -EINVAL when the source subdevice could not be resolved from the media graph, before pmruntimeresumeandget() and mediapipelinestart() had been called. The remaining error paths already converge on the errbufferdone label, which calls dcmippbytecapallbuffersdone(..., VB2BUFSTATEQUEUED). Jump to that label directly: the intermediate errpmput / errmediapipelinestop 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 startstreaming() failure").
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
If start_streaming() fails (e.g., returns -EINVAL), ensure queued VB2 buffers are returned/finished via vb2_buffer_done()/dcmipp_bytecap_all_buffers_done(...) on the start_streaming error path so buffers do not leak (i.e., jump directly to the label that returns queued buffers on start_streaming() failure).
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68211?
The severity of CVE-2026-68211 is rated as 12, indicating a critical risk level.
How do I fix CVE-2026-68211?
To fix CVE-2026-68211, update your Linux kernel to the latest version where this vulnerability has been addressed.
What systems are affected by CVE-2026-68211?
CVE-2026-68211 affects systems running an affected version of the Linux kernel that utilizes the stm32-dcmipp driver.
What are the potential consequences of CVE-2026-68211?
Exploiting CVE-2026-68211 could lead to data loss as buffers may not be returned correctly in the event of a streaming failure.
When was CVE-2026-68211 published?
CVE-2026-68211 was published on August 10, 2026.