# CVE-2026-93170: dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers

> A race condition in Xilinx DMA drivers allows premature transfer attempts, potentially causing descriptor corruption or denial of service.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-103028, BELL-CVE-2026-93170, DEBIAN-CVE-2026-93170, GHSA-mc6p-4g8q-qv3v, UBUNTU-CVE-2026-93170

## What is CVE-2026-93170?

CVE-2026-93170 is a high-severity vulnerability in Linux, published on 17 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: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers

Fix a race condition in AXIDMA and MCDMA irq handlers where the channel
could be incorrectly marked as idle and attempt spurious transfers when
descriptors are still being processed.

The issue occurs when:
1. Multiple descriptors are queued and active.
2. An interrupt fires after completing some descriptors.
3. xilinx_dma_complete_descriptor() moves completed descriptors to
done_list.
4. Channel is marked idle and start_transfer() is called even though
   active_list still contains unprocessed descriptors.
5. This leads to premature transfer attempts and potential descriptor
   corruption or missed completions.

Only mark the channel as idle and start new transfers when the active list
is actually empty, ensuring proper channel state management and avoiding
spurious transfer attempts.

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


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

Apply the vendor's patch.

## Is CVE-2026-93170 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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