# CVE-2026-97507: media: dm1105: fix missing error check for dma_alloc_coherent

> A missing error check in the dm1105 media driver allows a local attacker to cause a kernel crash via null pointer dereference.

- **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:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-103565, BELL-CVE-2026-97507, DEBIAN-CVE-2026-97507, GHSA-5qvr-cjrj-5r5p, UBUNTU-CVE-2026-97507

## What is CVE-2026-97507?

CVE-2026-97507 is a vulnerability in Linux, published on 24 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: dm1105: fix missing error check for dma_alloc_coherent

The return value of dm1105_dma_map(), which handles DMA memory allocation,
is ignored in dm1105_hw_init(). If dma_alloc_coherent() fails, the driver
will proceed using a NULL pointer for DMA transfers, leading to a kernel
oops or invalid hardware access.

Fix this by checking the return value and propagating -ENOMEM on failure.

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


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

Apply the vendor's patch.

## Is CVE-2026-97507 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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