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-68215media: radio-si476x: Unregister v4l2_device on probe failure

Description

In the Linux kernel, the following vulnerability has been resolved: media: radio-si476x: Unregister v4l2_device on probe failure si476x_radio_probe() registers radio->v4l2dev before allocating the V4L2 controls and before registering the video device. If any of those later steps fails, probe returns through the exit label after freeing only the control handler. A failed probe does not call si476x_radio_remove(), so the v4l2_device_unregister() there is not reached. This leaves the parent device reference taken by v4l2_device_register() behind on the error path. Unregister the V4L2 device in the probe error path after freeing the controls.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 9 days 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 87% of all CVEs (18 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 b879a9c2a755d4ddf9e685258de6435710fd2f03 – < 828f8d2181aa09ff3d8b67e1d9c92d0dfc81026f
    • affected b879a9c2a755d4ddf9e685258de6435710fd2f03 – < cac1c4f08cb2d8beaad16f7ddc7911f3711daa9f
    • affected b879a9c2a755d4ddf9e685258de6435710fd2f03 – < 7cf393f176317a126d71e88e4b6e25e83499b465
    • affected b879a9c2a755d4ddf9e685258de6435710fd2f03 – < 4ca9c9f12b1bc341a0a3bbbd2090fd182db53771
    • affected b879a9c2a755d4ddf9e685258de6435710fd2f03 – < 7ef9f1659404544a8dddd68842bafcb4a38197af
    • affected b879a9c2a755d4ddf9e685258de6435710fd2f03 – < 64cb15878b35e5574ff4f80a0b613a79e47867ba
    • affected b879a9c2a755d4ddf9e685258de6435710fd2f03 – < 730c235d7d2c80a401dac56b0f5066c889aa442d
    • affected b879a9c2a755d4ddf9e685258de6435710fd2f03 – < 436a693af04ffb889aaf87cb69ec1f2b21d3569c
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .