Menu

Star on GitHub · 3.2k

CVE-2026-68203

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 devic…

Published Aug 10, 2026EPSS 0.21%

Overview

CVE-2026-68203 is a known-severity vulnerability. It was published on August 10, 2026.

Technical description

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 s

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-68203?

CVE-2026-68203 is a known-severity vulnerability. It was published on August 10, 2026.

How severe is CVE-2026-68203?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-68203?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-68203?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-68203 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.