https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 16:01:39 +0000 https://vulnerability.circl.lu/vuln/cve-2026-68203 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: vivid: fix cleanup bugs in vivid_init()</p> <p>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:</p> <p>vivid_init() -&gt; platform_device_register(&amp;vivid_pdev) -&gt; device_initialize(&amp;vivid_pdev.dev) -&gt; setup_pdev_dma_masks(&amp;vivid_pdev) -&gt; platform_device_add(&amp;vivid_pdev)</p> <p>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.</p> <p>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.</p> <p>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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: vivid: fix cleanup bugs in vivid_init()</p> <p>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:</p> <p>vivid_init() -&gt; platform_device_register(&amp;vivid_pdev) -&gt; device_initialize(&amp;vivid_pdev.dev) -&gt; setup_pdev_dma_masks(&amp;vivid_pdev) -&gt; platform_device_add(&amp;vivid_pdev)</p> <p>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.</p> <p>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.</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-68203