Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68217media: pwc: Drain fill_buf on start_streaming() failure

Description

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/

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 885fe18f5542fe283a17f70583383c6cadcba1c3 – < 97f3c15957ec7e6d249f05407ad947c0644df24d
    • affected 885fe18f5542fe283a17f70583383c6cadcba1c3 – < a4afffd148991a826e8995362fb10cf8705c1130
    • affected 885fe18f5542fe283a17f70583383c6cadcba1c3 – < eabe9a59640698137d7382d5b549e95dc37f7565
    • affected 885fe18f5542fe283a17f70583383c6cadcba1c3 – < a56e7641e09bd80b976e944ae759109b86fd5b38
    • affected 885fe18f5542fe283a17f70583383c6cadcba1c3 – < acc789b2173070638cad89c2b61d33ed338be0dd
    • affected 885fe18f5542fe283a17f70583383c6cadcba1c3 – < 9afd605dcd96c7a45f338eded1de16679b30e1df
    • affected 885fe18f5542fe283a17f70583383c6cadcba1c3 – < 5d4812668b03f823b5044789d6aa77fe56b42587
    • affected 885fe18f5542fe283a17f70583383c6cadcba1c3 – < 906e410dcffbbd99fb4081abab817a830033aa28
  • Linux · Linux

    • affected 3.1
    • unaffected < 3.1
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68217 badge
[![CVE-2026-68217](https://cveledger.app/badge/CVE-2026-68217.svg)](https://cveledger.app/cve/CVE-2026-68217)

Record last updated .