CVE Catalog

CVE-2026-68203

Low risk· EPSS 11%
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.21%

11th percentile - higher than 11% of all known CVEs

Summary

In the Linux kernel, in the vivid driver, there are cleanup bugs in vivid_init(). When platform_device_register() fails, the embedded struct device in vivid_pdev has already been initialized, but the failure path does not drop the device reference, leading to a reference leak. Additionally, the unreg_driver label incorrectly calls platform_driver_register() instead of platform_driver_unregister(), breaking cleanup when workqueue creation fails after successful driver registration.

Risk Assessment

Reference leaks and incorrect cleanup can lead to memory and resource management issues, potentially causing system instability or hard-to-diagnose errors.

Recommendation

Apply the Linux kernel patch that adds a platform_device_put() call before jumping to the common cleanup path and fixes the call in the unreg_driver label to platform_driver_unregister().

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS