CVE-2026-68203 Affecting linux-6.12 package, versions <6.12.101-1~deb12u1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-LINUX612-18912514
- published18 Aug 2026
- disclosed10 Aug 2026
Introduced: 10 Aug 2026
CVE-2026-68203 (opens in a new tab)How to fix?
Upgrade Echo:latest linux-6.12 to version 6.12.101-1~deb12u1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream linux-6.12 package and not the linux-6.12 package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
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.
References
- https://advisory.echohq.com/cve/CVE-2026-68203
- https://git.kernel.org/stable/c/1349af7f87df57940619f5b87990b799dac9ed8a
- https://git.kernel.org/stable/c/4385092a86b94e1f332db35a3766108978c0722f
- https://git.kernel.org/stable/c/6d51ad8f1c50c50d1abcc97fd243179967184c6a
- https://git.kernel.org/stable/c/a07c179a92e949172ca52f6d4a13202ea88cd4b7