# CVE-2026-72148: dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK

> Concurrent DMA channel operations can cause race conditions in shared interrupt mask registers, potentially leading to system instability or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/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:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-72148, DEBIAN-CVE-2026-72148, GHSA-wjmg-69jj-9p9g, UBUNTU-CVE-2026-72148

## What is CVE-2026-72148?

CVE-2026-72148 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: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK

The DONE_INT_MASK and ABORT_INT_MASK registers are shared by all DMA
channels, and modifying them requires a read-modify-write sequence.
Because this operation is not atomic, concurrent calls to
dw_edma_v0_core_start() can introduce race conditions if two channels
update these registers simultaneously.

Add a spinlock to serialize access to these registers and prevent race
conditions.

[den: update dw_edma.lock comment]

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


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

Apply the vendor's patch.

## Is CVE-2026-72148 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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