# CVE-2026-68207: media: ti: vpe: unwind v4l2 device registration on probe error

> A resource leak in the TI VPE driver probe error path can lead to system instability 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-68207, DEBIAN-CVE-2026-68207, GHSA-9fcx-rhjm-5qjm, UBUNTU-CVE-2026-68207

## What is CVE-2026-68207?

CVE-2026-68207 is a 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: ti: vpe: unwind v4l2 device registration on probe error

If the vpe_top resource is missing, vpe_probe() returns -ENODEV after
v4l2_device_register() has succeeded. Probe failures do not call the
driver's remove callback, so the v4l2 device remains registered on that
error path.

Route that failure through the existing v4l2_device_unregister() unwind
label, matching the other errors after v4l2_device_register().

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


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

Apply the vendor's patch.

## Is CVE-2026-68207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68207 is a 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-68207 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-68207/ (Markdown: https://insights.sbomify.com/CVE-2026-68207/index.md)
```

## Sources

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

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