# CVE-2026-89896: media: cedrus: fix memory leak in cedrus_init_ctrls()

> A memory leak in the Cedrus VPU driver allows local attackers to exhaust kernel memory, potentially 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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101565, BELL-CVE-2026-89896, DEBIAN-CVE-2026-89896, GHSA-832p-ggr6-5385, UBUNTU-CVE-2026-89896

## What is CVE-2026-89896?

CVE-2026-89896 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: cedrus: fix memory leak in cedrus_init_ctrls()

In cedrus_init_ctrls(), the V4L2 control handler is initialized before
allocating memory for ctx->ctrls. If this allocation fails, the function
returns -ENOMEM without freeing the previously allocated handler
resources, leading to a memory leak.

Fix this by calling v4l2_ctrl_handler_free() on the ctx->ctrls allocation
failure path.

The bug was first flagged by an experimental analysis tool we are
developing for kernel memory-management bugs while analyzing
v6.13-rc1. The tool is still under development and is not yet publicly
available. Manual inspection confirms that the bug is still
present in v7.1.1.

An x86_64 allyesconfig build showed no new warnings. As we do not have an
Allwinner SoC or board with a Cedrus VPU available to test with, no
runtime testing was able to be performed.

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


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

Apply the vendor's patch.

## Is CVE-2026-89896 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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