# CVE-2026-89886: media: intel/ipu6: fix async notifier cleanup leak on parse error

> A memory leak in the Intel IPU6 kernel driver allows local attackers to cause a denial of service by triggering a parse error during initialization.

- **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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89886, DEBIAN-CVE-2026-89886, GHSA-3gm6-jh34-23qh, UBUNTU-CVE-2026-89886

## What is CVE-2026-89886?

CVE-2026-89886 is a memory corruption vulnerability in Linux, published on 16 Sep 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: intel/ipu6: fix async notifier cleanup leak on parse error

isys_notifier_init() calls v4l2_async_nf_init() and then adds fwnode
remote subdevs in a loop with v4l2_async_nf_add_fwnode_remote(). If an
endpoint parse or add fails partway through the loop, it jumps to
err_parse and returns without calling v4l2_async_nf_cleanup(), leaking
every v4l2_async_connection already added to the notifier's waiting
list.

The register-failure path just below already cleans up correctly, and
the caller only tears the notifier down (isys_notifier_cleanup()) once
isys_notifier_init() has returned success. Clean up the notifier on the
parse error path too.

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


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

Apply the vendor's patch.

## Is CVE-2026-89886 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89886 is a memory corruption vulnerability in Linux, published on 16 Sep 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-89886 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-89886/ (Markdown: https://insights.sbomify.com/CVE-2026-89886/index.md)
```

## Sources

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

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