# CVE-2026-68221: media: nuvoton: npcm-video: fix memory leaks in probe and remove

> A memory leak in the Nuvoton NPCM video driver allows attackers to cause denial of service by exhausting kernel memory through repeated device binding or unbinding.

- **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:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68221, DEBIAN-CVE-2026-68221, GHSA-pm6p-p8m3-vpmm, UBUNTU-CVE-2026-68221

## What is CVE-2026-68221?

CVE-2026-68221 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: nuvoton: npcm-video: fix memory leaks in probe and remove

npcm_video_probe() allocates the npcm_video structure with kzalloc_obj()
but never frees it on any probe error path or in npcm_video_remove(),
leaking the allocation on every failed probe and every normal unbind.

Additionally, when npcm_video_setup_video() fails, the reserved memory
association established by of_reserved_mem_device_init() in
npcm_video_init() is not released, leaking the rmem_assigned_device
entry on the global list.

Fix both by adding kfree(video) to all probe error paths and to
npcm_video_remove(), and adding the missing
of_reserved_mem_device_release() call when npcm_video_setup_video()
fails.

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


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

Apply the vendor's patch.

## Is CVE-2026-68221 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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