CVE-2026-68215

media: radio-si476x: Unregister v4l2_device on probe failure

N/A
Published: August 10, 2026 at 12:00 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.10 ≤ v < 5.10.2653.10 ≤ v < 5.15.2163.10 ≤ v < 6.1.1833.10 ≤ v < 6.12.1013.10 ≤ v < 6.18.423.10 ≤ v < 6.6.1483.10 ≤ v < 7.1.63.10 ≤ v < 7.23.10b879a9c2a755d4ddf9e685258de6435710fd2f03
Vendor states this is fixed in 436a693af04ffb889aaf87cb69ec1f2b21d3569c (fixed)
Vendor states this is fixed in 4ca9c9f12b1bc341a0a3bbbd2090fd182db53771 (fixed)
Vendor states this is fixed in 64cb15878b35e5574ff4f80a0b613a79e47867ba (fixed)
Vendor states this is fixed in 730c235d7d2c80a401dac56b0f5066c889aa442d (fixed)
Vendor states this is fixed in 7cf393f176317a126d71e88e4b6e25e83499b465 (fixed)
Vendor states this is fixed in 7ef9f1659404544a8dddd68842bafcb4a38197af (fixed)
Vendor states this is fixed in 828f8d2181aa09ff3d8b67e1d9c92d0dfc81026f (fixed)
Vendor states this is fixed in cac1c4f08cb2d8beaad16f7ddc7911f3711daa9f (fixed)
Vendor states this is fixed in 3.10 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card