CVE-2026-68203
CVE CVE-2026-68203EUVD EUVD-2026-55304Published 2026-08-10T12:00:22.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux f46d740fb0258982f00ffdbddc6486e674edafb5 <a07c179a92e949172ca52f6d4a13202ea88cd4b7; patch: 6.12.101; f46d740fb0258982f00ffdbddc6486e674edafb5 <4385092a86b94e1f332db35a3766108978c0722f; 4.1; patch: 7.1.6; patch: 6.18.42; f46d740fb0258982f00ffdbddc6486e674edafb5 <6d51ad8f1c50c50d1abcc97fd243179967184c6a; f46d740fb0258982f00ffdbddc6486e674edafb5 <1349af7f87df57940619f5b87990b799dac9ed8a; patch: 7.2-rc1; patch: 0
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.