VulnerabilityPublished 10 Aug 2026Updated 21 Oct 2026

CVE-2026-68203: Linux kernel · media: vivid: fix cleanup bugs in vivid_init()

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in ae6ccae32f51f788035d2c5cec898491dd7150ef : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:30 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in ae6ccae32f51f788035d2c5cec898491dd7150ef, a07c179a92e949172ca52f6d4a13202ea88cd4b7, 4385092a86b94e1f332db35a3766108978c0722f +2

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ f46d740fb0258982f00ffdbddc6486e674edafb5, < ae6ccae32f51f788035d2c5cec898491dd7150ef	Fixed in ae6ccae32f51f788035d2c5cec898491dd7150ef
LinuxLinux	Affected ≥ f46d740fb0258982f00ffdbddc6486e674edafb5, < a07c179a92e949172ca52f6d4a13202ea88cd4b7	Fixed in a07c179a92e949172ca52f6d4a13202ea88cd4b7
LinuxLinux	Affected ≥ f46d740fb0258982f00ffdbddc6486e674edafb5, < 4385092a86b94e1f332db35a3766108978c0722f	Fixed in 4385092a86b94e1f332db35a3766108978c0722f
LinuxLinux	Affected ≥ f46d740fb0258982f00ffdbddc6486e674edafb5, < 1349af7f87df57940619f5b87990b799dac9ed8a	Fixed in 1349af7f87df57940619f5b87990b799dac9ed8a
LinuxLinux	Affected ≥ f46d740fb0258982f00ffdbddc6486e674edafb5, < 6d51ad8f1c50c50d1abcc97fd243179967184c6a	Fixed in 6d51ad8f1c50c50d1abcc97fd243179967184c6a
LinuxLinux	Affected =4.1	Fixed in–

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 static analysis tool I developed and confirmed by manual review. The incorrect cleanup call was found during code inspection.

References

Community reviews

Loading reviews…