CVE-2026-93170: dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0b6d055edb55ecadadf54e930c2b4fab76fa9a5a, 425630e9eea1f9f8912b8c6abf01e0dab1e27917, 5459e02707b27a964ae72e028d3ff72a3b687c4a.
Low priority for now. Upgrade to Linux Linux 0b6d055edb55ecadadf54e930c2b4fab76fa9a5a, 425630e9eea1f9f8912b8c6abf01e0dab1e27917, 5459e02707b27a964ae72e028d3ff72a3b687c4a or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.7affected
- c0bba3a99f0709c24c2c7ada7cb098966b1d791f and later · before 7f4b989d7d87381927b98d64492f8dcf979f57abaffected · git
- c0bba3a99f0709c24c2c7ada7cb098966b1d791f and later · before 5459e02707b27a964ae72e028d3ff72a3b687c4aaffected · git
- c0bba3a99f0709c24c2c7ada7cb098966b1d791f and later · before 425630e9eea1f9f8912b8c6abf01e0dab1e27917affected · git
- c0bba3a99f0709c24c2c7ada7cb098966b1d791f and later · before fdaf297ab275c6efecac5e87669c31bc89b74297affected · git
- c0bba3a99f0709c24c2c7ada7cb098966b1d791f and later · before c27d16fd2358b2fc3e1ffaca03afd11dc28630eaaffected · git
- c0bba3a99f0709c24c2c7ada7cb098966b1d791f and later · before ec927657524be4438447944a58173c7baf7f2384affected · git
- c0bba3a99f0709c24c2c7ada7cb098966b1d791f and later · before c3e943490ced0b9ad475844eda7661f6a9bcfb4aaffected · git
- c0bba3a99f0709c24c2c7ada7cb098966b1d791f and later · before 0b6d055edb55ecadadf54e930c2b4fab76fa9a5aaffected · git
- before 4.7not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93168Sep 17, 2026 · dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout0Monitor
- ← EarlierCVE-2026-93169Sep 17, 2026 · dmaengine: zynqmp_dma: fix race between runtime PM and device removal0Monitor
- Later →CVE-2026-93171Sep 17, 2026 · leds: lp5860: Fix a potential double-unlock0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0b6d055edb55ecadadf54e930c2b4fab76fa9a5a | Vendor (CNA) |
| Linux Linux | 425630e9eea1f9f8912b8c6abf01e0dab1e27917 | Vendor (CNA) |
| Linux Linux | 5459e02707b27a964ae72e028d3ff72a3b687c4a | Vendor (CNA) |
| Linux Linux | 7f4b989d7d87381927b98d64492f8dcf979f57ab | Vendor (CNA) |
| Linux Linux | c27d16fd2358b2fc3e1ffaca03afd11dc28630ea | Vendor (CNA) |
| Linux Linux | c3e943490ced0b9ad475844eda7661f6a9bcfb4a | Vendor (CNA) |
| Linux Linux | ec927657524be4438447944a58173c7baf7f2384 | Vendor (CNA) |
| Linux Linux | fdaf297ab275c6efecac5e87669c31bc89b74297 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/425630e9eea1f9f8912b8c6abf01e0dab1e27917
- git.kernel.org/stable/c/5459e02707b27a964ae72e028d3ff72a3b687c4a
- git.kernel.org/stable/c/7f4b989d7d87381927b98d64492f8dcf979f57ab
- git.kernel.org/stable/c/c27d16fd2358b2fc3e1ffaca03afd11dc28630ea
- git.kernel.org/stable/c/c3e943490ced0b9ad475844eda7661f6a9bcfb4a
- git.kernel.org/stable/c/ec927657524be4438447944a58173c7baf7f2384
- git.kernel.org/stable/c/fdaf297ab275c6efecac5e87669c31bc89b74297
Vendor advisories and official records. Exploit/PoC links are deliberately left out.