# CVE-2026-68215: media: radio-si476x: Unregister v4l2_device on probe failure

> A missing unregister call in the si476x radio driver probe error path leaves a dangling reference, potentially causing memory corruption or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68215, DEBIAN-CVE-2026-68215, GHSA-gwv8-m63h-cvjc, UBUNTU-CVE-2026-68215

## What is CVE-2026-68215?

CVE-2026-68215 is a memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-68215?


## How do I fix CVE-2026-68215?

Apply the vendor's patch.

## Is CVE-2026-68215 being exploited?

There is no known exploitation of CVE-2026-68215 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68215 and fix it if it is affected.

What it is: CVE-2026-68215 is a memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68215 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68215/ (Markdown: https://insights.sbomify.com/CVE-2026-68215/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68215
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68215
- OSV: https://osv.dev/vulnerability/CVE-2026-68215

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68215/
Summaries are generated and may contain mistakes; the official description above is the record.