CVE-2026-68216: Linux kernel · media: pwc: Return queued buffers on start_streaming() failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.8 High · fixed in fa78e590852751d3ad32f33f6b4e210fe6ccbe9b : patch Linux kernel soon.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in fa78e590852751d3ad32f33f6b4e210fe6ccbe9b, f2f9fcacd81953dde6cb86312ab13ca13e689664, d552852bf76b7dfb35b4593fc874d8dd2f1b1bf3 +5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: media: pwc: 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. pwc's start_streaming() had two early returns that hit this trap: -ENODEV when the USB device was already disconnected, and -ERESTARTSYS when mutex_lock_interruptible() was interrupted by a signal. Call the existing pwc_cleanup_queued_bufs() helper with VB2_BUF_STATE_QUEUED before returning (matching the state already used by the pwc_isoc_init() error path in the same function). This mirrors the uvcvideo fix in commit 4cf3b6fd54eb ("media: uvcvideo: Return queued buffers on start_streaming() failure").
References
- git.kernel.org/stable/c/d552852bf76b7dfb35b4593fc874d8dd2f1b1bf3 (opens in a new tab)
- git.kernel.org/stable/c/0362ae30b61b3053ee3095c1b8f179197ec4f539 (opens in a new tab)
- git.kernel.org/stable/c/fa78e590852751d3ad32f33f6b4e210fe6ccbe9b (opens in a new tab)
- git.kernel.org/stable/c/f2f9fcacd81953dde6cb86312ab13ca13e689664 (opens in a new tab)
- git.kernel.org/stable/c/5d7cc2634c3843a1414a0f6407aa17f1f91dee60 (opens in a new tab)
- git.kernel.org/stable/c/cb16b79a2be2cec9c3ebe4147490817c4d8b1de3 (opens in a new tab)
- git.kernel.org/stable/c/a4f8f629983f643333e49df90557805469bcbb25 (opens in a new tab)
- git.kernel.org/stable/c/975b2ee20e569d47821e4f6c9761b4664d48a6a4 (opens in a new tab)