CVE-2026-68217media: pwc: Drain fill_buf on start_streaming() failure
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: media: pwc: Drain fill_buf on start_streaming() failure pwc_isoc_init() submits its isochronous URBs with usb_submit_urb(.., GFP_KERNEL) in a loop. After the first URB is submitted, its completion handler pwc_isoc_handler() can run on another CPU before the loop finishes: start_streaming() pwc_isoc_init() usb_submit_urb(urbs[0], GFP_KERNEL) pwc_isoc_handler(urbs[0]) pdev->fill_buf = pwc_get_next_fill_buf(pdev) usb_submit_urb(urbs[i>0], ..) -> fails pwc_isoc_cleanup(pdev) /* kills URBs */ return ret; pwc_cleanup_queued_bufs(pdev, VB2_BUF_STATE_QUEUED) pwc_get_next_fill_buf() detaches a buffer from pdev->queued_bufs and stores it in pdev->fill_buf. The error path in start_streaming() only drains pdev->queued_bufs, so the buffer parked in pdev->fill_buf is leaked. vb2_start_streaming() then triggers WARN_ON(owned_by_drv_count). stop_streaming() already handles this since commit 80b0963e1698 ("[media] pwc: fix WARN_ON"), which added the fill_buf drain in the teardown path but not in the start_streaming() error path. Mirror that handling on failure so start_streaming() returns with no buffer owned by the driver. Issue identified by automated review of the INV-003 series at https://sashiko.dev/
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | 885fe18f5542fe283a17f70583383c6cadcba1c3 builds before 97f3c15957ec7e6d249f05407ad947c0644df24d; from 885fe18f5542fe283a17f70583383c6cadcba1c3 before a4afffd148991a826e8995362fb10cf8705c1130; from 885fe18f5542fe283a17f70583383c6cadcba1c3 before eabe9a59640698137d7382d5b549e95dc37f7565; from 885fe18f5542fe283a17f70583383c6cadcba1c3 before a56e7641e09bd80b976e944ae759109b86fd5b38; from 885fe18f5542fe283a17f70583383c6cadcba1c3 before acc789b2173070638cad89c2b61d33ed338be0dd; 885fe18f5542fe283a17f70583383c6cadcba1c3 builds before 9afd605dcd96c7a45f338eded1de16679b30e1df; 885fe18f5542fe283a17f70583383c6cadcba1c3 builds before 5d4812668b03f823b5044789d6aa77fe56b42587; from 885fe18f5542fe283a17f70583383c6cadcba1c3 before 906e410dcffbbd99fb4081abab817a830033aa28 | CNA record |
References
- https://git.kernel.org/stable/c/97f3c15957ec7e6d249f05407ad947c0644df24d
- https://git.kernel.org/stable/c/a4afffd148991a826e8995362fb10cf8705c1130
- https://git.kernel.org/stable/c/eabe9a59640698137d7382d5b549e95dc37f7565
- https://git.kernel.org/stable/c/a56e7641e09bd80b976e944ae759109b86fd5b38
- https://git.kernel.org/stable/c/acc789b2173070638cad89c2b61d33ed338be0dd
- https://git.kernel.org/stable/c/9afd605dcd96c7a45f338eded1de16679b30e1df
- https://git.kernel.org/stable/c/5d4812668b03f823b5044789d6aa77fe56b42587
- https://git.kernel.org/stable/c/906e410dcffbbd99fb4081abab817a830033aa28
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.