CVE-2026-68209
Last modified
CVE-2026-68209 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: media: sun4i-csi: 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. sun4i_csi_start_streaming() returned -EINVAL when no matching CSI format could be found, before any setup (scratch buffer allocation, pipeline start) had been performed.
Description
In the Linux kernel, the following vulnerability has been resolved: media: sun4i-csi: 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. sun4i_csi_start_streaming() returned -EINVAL when no matching CSI format could be found, before any setup (scratch buffer allocation, pipeline start) had been performed. The remaining error paths already converge on the err_clear_dma_queue label, which calls return_all_buffers(..., VB2_BUF_STATE_QUEUED) under csi->qlock. Jump to that label directly: the intermediate err_disable_device / err_disable_pipeline / err_free_scratch_buffer 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 | >= 577bbf23b758848f0c4a50d346460b690c753024, < 4872161e6fbe4e1783daea8bff79caddfae0fb82; >= 577bbf23b758848f0c4a50d346460b690c753024, < a8abecc638a7feb20b78fabd563b05e30c071331; >= 577bbf23b758848f0c4a50d346460b690c753024, < b5184b3f0e9d4cc47059ba1138c9a73d43d2493f; >= 577bbf23b758848f0c4a50d346460b690c753024, < 668face37fdb6b6900645dc8777195498541c9a7; >= 577bbf23b758848f0c4a50d346460b690c753024, < bbba3e260a62810a717b4442a3bb96d0ec0f6309 |
| Linux | Linux | 5.4 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68209?
How severe is CVE-2026-68209?
How do I fix CVE-2026-68209?
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-68203In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68204In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68205In the Linux kernel, the following vulnerability has been re…
- 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-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-68211In 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…
Are you affected by CVE-2026-68209?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
