CVE-2026-68211
Last modified
CVE-2026-68211 is a vulnerability of currently unknown severity. 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).
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").
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 28e0f37722965fa150af31d82101c95fd21aef60, < ed342a86bb2f9c1b44a0fc4f6b08c14073946e4f; >= 28e0f37722965fa150af31d82101c95fd21aef60, < 624af2d4b5e9d3dd366538e4fb4a2a037792a7e3; >= 28e0f37722965fa150af31d82101c95fd21aef60, < ffc8eec06378a340d708c889184ab3e14b57d540 |
| Linux | Linux | 6.8 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68211?
How severe is CVE-2026-68211?
How do I fix CVE-2026-68211?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68206In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68207In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68208In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68209In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6821GitLab has remediated an issue in GitLab EE affecting all ve…4.3
- CVE-2026-68210In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68212In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68213In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68214In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68215In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68216In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68217In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68211?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
