# CVE-2026-72146: dmaengine: sh: rz-dmac: Move interrupt request after everything is set up

> A race condition in the RZ-DMAC driver allows invalid memory access if an interrupt fires before initialization, potentially causing a kernel crash.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** 15 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-72146, DEBIAN-CVE-2026-72146, GHSA-87f6-c6f3-59h3, UBUNTU-CVE-2026-72146

## What is CVE-2026-72146?

CVE-2026-72146 is a high-severity 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: sh: rz-dmac: Move interrupt request after everything is set up

Once the interrupt is requested, the interrupt handler may run immediately.
Since the IRQ handler can access channel->ch_base, which is initialized
only after requesting the IRQ, this may lead to invalid memory access.
Likewise, the IRQ thread may access uninitialized data (the ld_free,
ld_queue, and ld_active lists), which may also lead to issues.

Request the interrupts only after everything is set up. To keep the error
path simpler, use dmam_alloc_coherent() instead of dma_alloc_coherent().

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


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

Apply the vendor's patch.

## Is CVE-2026-72146 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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