# CVE-2026-72147: dmaengine: dw-edma-pcie: Reject devices without driver data

> A local attacker can cause a kernel crash by binding a device without driver data to the dw-edma-pcie driver, leading to a NULL pointer dereference.

- **Severity:** Not scored
- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72147, DEBIAN-CVE-2026-72147, GHSA-47f2-6xxj-8w97, UBUNTU-CVE-2026-72147

## What is CVE-2026-72147?

CVE-2026-72147 is a vulnerability in Linux, published on 15 Aug 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: dw-edma-pcie: Reject devices without driver data

dw_edma_pcie_probe() treats the PCI device ID driver_data as the
template for the controller layout and copies it unconditionally. A
device bound dynamically via sysfs can match the driver without that
data, which leads to a NULL pointer dereference.

Reject such matches before enabling the device.

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


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

Apply the vendor's patch.

## Is CVE-2026-72147 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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