Skip to main content
VulnerabilityPublished Updated

CVE-2026-68211: Linux kernel · media: stm32-dcmipp: Return queued buffers on start_streaming() failure

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in ffc8eec06378a340d708c889184ab3e14b57d540 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in ffc8eec06378a340d708c889184ab3e14b57d540, ed342a86bb2f9c1b44a0fc4f6b08c14073946e4f, c1800238a60b0584b1924f11ce38ec8aba533238 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to ffc8eec06378a340d708c889184ab3e14b57d540, ed342a86bb2f9c1b44a0fc4f6b08c14073946e4f, c1800238a60b0584b1924f11ce38ec8aba533238 or 624af2d4b5e9d3dd366538e4fb4a2a037792a7e3.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 28e0f37722965fa150af31d82101c95fd21aef60, < ffc8eec06378a340d708c889184ab3e14b57d540
Fixed in
  • ffc8eec06378a340d708c889184ab3e14b57d540
LinuxLinuxAffected
  • ≥ 28e0f37722965fa150af31d82101c95fd21aef60, < ed342a86bb2f9c1b44a0fc4f6b08c14073946e4f
Fixed in
  • ed342a86bb2f9c1b44a0fc4f6b08c14073946e4f
LinuxLinuxAffected
  • ≥ 28e0f37722965fa150af31d82101c95fd21aef60, < c1800238a60b0584b1924f11ce38ec8aba533238
Fixed in
  • c1800238a60b0584b1924f11ce38ec8aba533238
LinuxLinuxAffected
  • ≥ 28e0f37722965fa150af31d82101c95fd21aef60, < 624af2d4b5e9d3dd366538e4fb4a2a037792a7e3
Fixed in
  • 624af2d4b5e9d3dd366538e4fb4a2a037792a7e3
LinuxLinuxAffected
  • =6.8
Fixed in–

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").

References

Community reviews

Loading reviews…