# CVE-2026-89522: media: staging/ipu7: fix async notifier UAF on probe error path

> A use-after-free vulnerability in the Linux kernel IPU7 driver allows attackers to cause memory corruption and potential code execution via a probe error path.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89522, DEBIAN-CVE-2026-89522, GHSA-p4hr-jw27-vj7c, UBUNTU-CVE-2026-89522

## What is CVE-2026-89522?

CVE-2026-89522 is a high-severity use after free vulnerability in Linux, published on 11 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: staging/ipu7: fix async notifier UAF on probe error path

isys_register_devices() registers the V4L2 async notifier via
isys_notifier_init(). If a subsequent probe step such as
isys_fw_log_init() fails, isys_probe() jumps to the out_cleanup label
which only calls isys_unregister_devices(). That helper tears down the
video devices, subdevices, V4L2 device and media device, but never
unregisters or cleans up the async notifier.

As a result the notifier stays chained in the global notifier_list while
the enclosing struct ipu7_isys is freed by devres, leading to list
corruption and a use-after-free the next time the list is walked.

The remove path already does the right thing by calling
isys_notifier_cleanup() before isys_unregister_devices(). Mirror that on
the probe error path so the notifier is unregistered and cleaned up
before the device is torn down.

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


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

Apply the vendor's patch.

## Is CVE-2026-89522 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89522 is a high-severity use after free vulnerability in Linux, published on 11 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-89522 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-89522/ (Markdown: https://insights.sbomify.com/CVE-2026-89522/index.md)
```

## Sources

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

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