Vulnerability · Published Aug 10, 2026 · Assigned by Linux

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

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 13% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 87.4% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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/

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.187-1DEBIAN-CVE-2026-68217
Debian:13linux6.12.101-1DEBIAN-CVE-2026-68217
Debian:14linux7.1.6-1DEBIAN-CVE-2026-68217
Debian:12linux-6.126.12.101-1~deb12u1DEBIAN-CVE-2026-68217
Ubuntu:22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux6.8.0-147.147UBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux7.0.0-38.38UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-aws6.8.0-1067.70UBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-aws7.0.0-1014.14UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure6.8.0-1071.79UBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-azure7.0.0-1017.17UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1017.17~24.04.1UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1069.76UBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1016.16UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-gcp6.8.0-1071.79UBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-gcp7.0.0-1014.14UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-gke5.15.0-1113.119UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-gke6.8.0-1066.74UBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-gke7.0.0-1008.9UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1100.108UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1052.56UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-38.38~24.04.4UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-ibm5.15.0-1111.115UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-ibm6.8.0-1067.68UBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-ibm7.0.0-1015.15UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1112.118UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-kvm5.15.0-1109.114UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-195.205UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-147.147.1UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1112.113UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1024.25~24.04.1UBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2022.23UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1070.72UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1059.59UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1015.15UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-oracle5.15.0-1114.120UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-oracle6.8.0-1064.67UBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-oracle7.0.0-1013.13UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-realtime7.0.0-38.38.1UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68217
Ubuntu:26.04:LTSlinux-riscv7.0.0-38.38.1UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-38.38.1~24.04.1UBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-vmware6.8.0-1008.8UBUNTU-CVE-2026-68217
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-68217
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1080.84UBUNTU-CVE-2026-68217

Affected products (as reported)

VendorProductVersions
Linux Linux 885fe18f5542fe283a17f70583383c6cadcba1c3 – before 97f3c15957ec7e6d249f05407ad947c0644df24d885fe18f5542fe283a17f70583383c6cadcba1c3 – before a4afffd148991a826e8995362fb10cf8705c1130885fe18f5542fe283a17f70583383c6cadcba1c3 – before eabe9a59640698137d7382d5b549e95dc37f7565885fe18f5542fe283a17f70583383c6cadcba1c3 – before a56e7641e09bd80b976e944ae759109b86fd5b38885fe18f5542fe283a17f70583383c6cadcba1c3 – before acc789b2173070638cad89c2b61d33ed338be0dd885fe18f5542fe283a17f70583383c6cadcba1c3 – before 9afd605dcd96c7a45f338eded1de16679b30e1df885fe18f5542fe283a17f70583383c6cadcba1c3 – before 5d4812668b03f823b5044789d6aa77fe56b42587885fe18f5542fe283a17f70583383c6cadcba1c3 – before 906e410dcffbbd99fb4081abab817a830033aa28
Linux Linux 3.1

References