# CVE-2026-68220: media: nxp: imx8-isi: Add missing v4l2_subdev_cleanup() in crossbar and pipe

> A memory leak in the NXP i.MX8 ISI driver allows local attackers to exhaust kernel memory by repeatedly loading and unloading the module, causing 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:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68220, DEBIAN-CVE-2026-68220, GHSA-gpmg-9cvg-r7vp, UBUNTU-CVE-2026-68220

## What is CVE-2026-68220?

CVE-2026-68220 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: nxp: imx8-isi: Add missing v4l2_subdev_cleanup() in crossbar and pipe

Both mxc_isi_crossbar_init() and mxc_isi_pipe_init() call
v4l2_subdev_init_finalize() which allocates the subdev active state,
but neither mxc_isi_crossbar_cleanup() nor mxc_isi_pipe_cleanup()
calls v4l2_subdev_cleanup() to free it.

This causes a memory leak on every rmmod, reported by kmemleak:

  unreferenced object 0xffff0000d06fc800 (size 192):
    comm "(udev-worker)", pid 254, jiffies 4294913455
    backtrace (crc 36eeae58):
      kmemleak_alloc+0x34/0x40
      __kvmalloc_node_noprof+0x5f8/0x7d8
      __v4l2_subdev_state_alloc+0x1fc/0x30c
      __v4l2_subdev_init_finalize+0x178/0x368

Add the missing v4l2_subdev_cleanup() calls before media_entity_cleanup()
in both crossbar and pipe cleanup paths.

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


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

Apply the vendor's patch.

## Is CVE-2026-68220 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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