# CVE-2026-89994: dmaengine: fsl-edma: tracing: no ptr dereference during log output

> A null pointer dereference in the fsl-edma tracing driver allows local attackers to crash the system by injecting events into the kernel trace buffer.

- **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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89994, DEBIAN-CVE-2026-89994, GHSA-2hx9-3cqh-fcjj, UBUNTU-CVE-2026-89994

## What is CVE-2026-89994?

CVE-2026-89994 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:

dmaengine: fsl-edma: tracing: no ptr dereference during log output

The fsl edma events store a pointer to a struct fsl_edma_engine in the
ringbuffer and dereference it when a log entry is printed. At this time,
the pointer may no longer be valid.

Event injection can be used to trigger a crash:

$ cd /sys/kernel/tracing
$ echo 'value = 0' > events/fsl_edma/edma_writeb/inject
$ cat trace

The log output needs only edma->membase. Add a membase field at the end
of the event and use the new field for log output. Keep the existing
fields for backward compatibility.

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


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

Apply the vendor's patch.

## Is CVE-2026-89994 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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