# CVE-2026-89995: dma-direct: return struct page from dma_direct_alloc_from_pool()

> A type confusion in the Linux kernel DMA allocator causes a null pointer dereference, leading to a system crash.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 21 Oct 2026
- **Also known as:** AZL-101649, BELL-CVE-2026-89995, DEBIAN-CVE-2026-89995, GHSA-36w9-6524-pc79, UBUNTU-CVE-2026-89995

## What is CVE-2026-89995?

CVE-2026-89995 is a high-severity 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:

dma-direct: return struct page from dma_direct_alloc_from_pool()

Commit 5b138c534fda ("dma-direct: factor out a dma_direct_alloc_from_pool
helper") changed dma_direct_alloc_from_pool() to return the CPU address
from dma_alloc_from_pool(). That fits dma_direct_alloc(), but
dma_direct_alloc_pages() also uses the helper and expects a struct page *.

Fix this by making dma_direct_alloc_from_pool() return the struct page *
again, and pass the CPU address back through an out-parameter for the
dma_direct_alloc() caller.

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


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

Apply the vendor's patch.

## Is CVE-2026-89995 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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