# CVE-2026-93223: staging: media: tegra-video: fix of_node_put() on VIP parse errors


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93223, DEBIAN-CVE-2026-93223, GHSA-f6j6-qc9x-24h7, UBUNTU-CVE-2026-93223

## What is CVE-2026-93223?

CVE-2026-93223 is a vulnerability in Linux, published on 24 Sep 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

staging: media: tegra-video: fix of_node_put() on VIP parse errors

tegra_vip_channel_of_parse() initializes np from dev->of_node without
taking a reference, but its error paths drop one through the
err_node_put label. This underflows the refcount of the VIP device's
OF node when endpoint parsing fails on a malformed device tree.

The only reference the function takes on np is the success-path
of_node_get() stored in vip->chan.of_node, and that one is already
released by the tegra_vip_init() error path and by tegra_vip_exit().

Return errors directly instead of jumping to the bogus cleanup label.

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


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

Upgrade to a fixed version.

## Is CVE-2026-93223 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93223 is a vulnerability in Linux, published on 24 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-93223 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-93223/ (Markdown: https://insights.sbomify.com/CVE-2026-93223/index.md)
```

## Sources

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

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