CVE-2026-68217: media: pwc: Drain fill_buf on start_streaming() failure
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 5d4812668b03f823b5044789d6aa77fe56b42587, 906e410dcffbbd99fb4081abab817a830033aa28, 97f3c15957ec7e6d249f05407ad947c0644df24d; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 5d4812668b03f823b5044789d6aa77fe56b42587, 906e410dcffbbd99fb4081abab817a830033aa28, 97f3c15957ec7e6d249f05407ad947c0644df24d; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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/
- Published
- Aug 10, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.1affected
- 885fe18f5542fe283a17f70583383c6cadcba1c3 and later · before 97f3c15957ec7e6d249f05407ad947c0644df24daffected · git
- 885fe18f5542fe283a17f70583383c6cadcba1c3 and later · before a4afffd148991a826e8995362fb10cf8705c1130affected · git
- 885fe18f5542fe283a17f70583383c6cadcba1c3 and later · before eabe9a59640698137d7382d5b549e95dc37f7565affected · git
- 885fe18f5542fe283a17f70583383c6cadcba1c3 and later · before a56e7641e09bd80b976e944ae759109b86fd5b38affected · git
- 885fe18f5542fe283a17f70583383c6cadcba1c3 and later · before acc789b2173070638cad89c2b61d33ed338be0ddaffected · git
- 885fe18f5542fe283a17f70583383c6cadcba1c3 and later · before 9afd605dcd96c7a45f338eded1de16679b30e1dfaffected · git
- 885fe18f5542fe283a17f70583383c6cadcba1c3 and later · before 5d4812668b03f823b5044789d6aa77fe56b42587affected · git
- 885fe18f5542fe283a17f70583383c6cadcba1c3 and later · before 906e410dcffbbd99fb4081abab817a830033aa28affected · git
- before 3.1not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68214Aug 10, 2026 · media: rtl2832: fix use-after-free in rtl2832_remove()0Monitor
- ← EarlierCVE-2026-68215Aug 10, 2026 · media: radio-si476x: Unregister v4l2_device on probe failure0Monitor
- Later →CVE-2026-68218Aug 10, 2026 · media: pci: dm1105: Free allocated workqueue0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 5d4812668b03f823b5044789d6aa77fe56b42587 | Vendor (CNA) |
| Linux Linux | 906e410dcffbbd99fb4081abab817a830033aa28 | Vendor (CNA) |
| Linux Linux | 97f3c15957ec7e6d249f05407ad947c0644df24d | Vendor (CNA) |
| Linux Linux | 9afd605dcd96c7a45f338eded1de16679b30e1df | Vendor (CNA) |
| Linux Linux | a4afffd148991a826e8995362fb10cf8705c1130 | Vendor (CNA) |
| Linux Linux | a56e7641e09bd80b976e944ae759109b86fd5b38 | Vendor (CNA) |
| Linux Linux | acc789b2173070638cad89c2b61d33ed338be0dd | Vendor (CNA) |
| Linux Linux | eabe9a59640698137d7382d5b549e95dc37f7565 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/906e410dcffbbd99fb4081abab817a830033aa28
- git.kernel.org/stable/c/97f3c15957ec7e6d249f05407ad947c0644df24d
- git.kernel.org/stable/c/9afd605dcd96c7a45f338eded1de16679b30e1df
- git.kernel.org/stable/c/a4afffd148991a826e8995362fb10cf8705c1130
- git.kernel.org/stable/c/a56e7641e09bd80b976e944ae759109b86fd5b38
- git.kernel.org/stable/c/acc789b2173070638cad89c2b61d33ed338be0dd
- git.kernel.org/stable/c/eabe9a59640698137d7382d5b549e95dc37f7565
Vendor advisories and official records. Exploit/PoC links are deliberately left out.