# CVE-2026-90405: media: stm32: dcmi: fix some error handling bugs in probe()

> A null pointer dereference in the STM32 DCMI driver probe function can cause a kernel crash, leading to 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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-90405, GHSA-8r39-p738-wgfm, UBUNTU-CVE-2026-90405

## What is CVE-2026-90405?

CVE-2026-90405 is a vulnerability in Linux, published on 17 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: stm32: dcmi: fix some error handling bugs in probe()

There are a few issues here:

1) After we assign:
        chan = dma_request_chan(&pdev->dev, "tx");
   Then the error paths need to clean up before returning.  The first
   error path does a direct return.
2) The error paths check "dcmi->mdma_chan" but that is not assigned
   until later so it results in memory leaks.  Test "mdma_chan"
   instead.
3) The error handling calls dma_release_channel(dcmi->dma_chan) before
   "dcmi->dma_chan" has been assigned which leads to a NULL pointer
   dereference.  Use the "chan" variable instead.

I also moved the call to dma_release_channel() after the call to
dma_release_channel() so it mirrors the allocation code better.

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


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

Apply the vendor's patch.

## Is CVE-2026-90405 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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