CVE-2026-68203

media: vivid: fix cleanup bugs in vivid_init()

CVE-2026-68203 is fixed in 15 products on 1 platform, first by DEBIAN-CVE-2026-68203, released August 11, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.5
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0022
11th percentile

In the Linux kernel, the following vulnerability has been resolved: media: vivid: fix cleanup bugs in vivid_init() When platform_device_register() fails in vivid_init(), the embedded struct device in vivid_pdev has already been initialized by device_initialize(), but the failure path jumps to free_output_strings without dropping the device reference for the current platform device: vivid_init() -> platform_device_register(&vivid_pdev) -> device_initialize(&vivid_pdev.dev) -> setup_pdev_dma_masks(&vivid_pdev) -> platform_device_add(&vivid_pdev) This leads to a reference leak when platform_device_register() fails. Fix this by calling platform_device_put() before jumping to the common cleanup path. Also, the unreg_driver label incorrectly calls platform_driver_register() instead of platform_driver_unregister(), which breaks cleanup when workqueue creation fails after successful driver registration. Fix that as well. The reference leak was identified by a static analysis tool I developed and confirmed by manual review. The incorrect cleanup call was found during code inspection.

Where it's fixed

ProductFixed inFixReleased
Linux
dtb-aarch64 · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-64kb · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-64kb · sles 16.0 6.12.0-160000.38.1 SUSE-SU-2026:23902-1 Sep 22, 2026
kernel-azure · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-azure · sles 16.0 6.12.0-160000.38.1 SUSE-SU-2026:23902-1 Sep 22, 2026
kernel-default · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-default · sles 16.0 6.12.0-160000.38.1 SUSE-SU-2026:23902-1 Sep 22, 2026
kernel-default-base · opensuse-leap 16.0 6.12.0-160000.38.1.160000.2.22 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-default-base · sles 16.0 6.12.0-160000.38.1.160000.2.23 SUSE-SU-2026:23902-1 Sep 22, 2026
kernel-docs · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-docs · sles 16.0 6.12.0-160000.38.1 SUSE-SU-2026:23902-1 Sep 22, 2026
kernel-kvmsmall · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-kvmsmall · sles 16.0 6.12.0-160000.38.1 SUSE-SU-2026:23902-1 Sep 22, 2026
kernel-obs-build · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-obs-qa · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-obs-qa · sles 16.0 6.12.0-160000.38.1 SUSE-SU-2026:23902-1 Sep 22, 2026
kernel-rt · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-source · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-source · sles 16.0 6.12.0-160000.38.1 SUSE-SU-2026:23902-1 Sep 22, 2026
kernel-syms · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-syms · sles 16.0 6.12.0-160000.38.1 SUSE-SU-2026:23902-1 Sep 22, 2026
kernel-zfcpdump · opensuse-leap 16.0 6.12.0-160000.38.1 OPENSUSE-SU-2026:21910-1 Sep 22, 2026
kernel-zfcpdump · sles 16.0 6.12.0-160000.38.1 SUSE-SU-2026:23902-1 Sep 22, 2026
linux · Debian 13.5 (trixie) 6.12.101-1 DEBIAN-CVE-2026-68203 Aug 11, 2026
linux · Debian 14 7.1.6-1 DEBIAN-CVE-2026-68203 Aug 11, 2026
linux-6.12 · Debian 12.15 (bookworm) 6.12.101-1~deb12u1 DEBIAN-CVE-2026-68203 Aug 11, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.