Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected f46d740fb0258982f00ffdbddc6486e674edafb5 – < 6c7307c1b45da4fef6b445ca5c113457d86a7806
    • affected f46d740fb0258982f00ffdbddc6486e674edafb5 – < ae6ccae32f51f788035d2c5cec898491dd7150ef
    • affected f46d740fb0258982f00ffdbddc6486e674edafb5 – < 4385092a86b94e1f332db35a3766108978c0722f
    • affected f46d740fb0258982f00ffdbddc6486e674edafb5 – < 1349af7f87df57940619f5b87990b799dac9ed8a
    • affected f46d740fb0258982f00ffdbddc6486e674edafb5 – < 6d51ad8f1c50c50d1abcc97fd243179967184c6a
    • affected f46d740fb0258982f00ffdbddc6486e674edafb5 – < a07c179a92e949172ca52f6d4a13202ea88cd4b7
  • Linux · Linux

    • affected 4.1
    • unaffected < 4.1
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68203 badge
[![CVE-2026-68203](https://cveledger.app/badge/CVE-2026-68203.svg)](https://cveledger.app/cve/CVE-2026-68203)

Record last updated .