CVE-2026-93170

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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:

  • Multiple descriptors are queued and active.
  • An interrupt fires after completing some descriptors.
  • xilinx_dma_complete_descriptor() moves completed descriptors to
done_list.
  • Channel is marked idle and start_transfer() is called even though
active_list still contains unprocessed descriptors.
  • 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.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (8)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b6d055edb55ecadadf54e930c2b4fab76fa9a5a
generic

dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3e943490ced0b9ad475844eda7661f6a9bcfb4a
generic

dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ec927657524be4438447944a58173c7baf7f2384
generic

dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c27d16fd2358b2fc3e1ffaca03afd11dc28630ea
generic

dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fdaf297ab275c6efecac5e87669c31bc89b74297
generic

dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/425630e9eea1f9f8912b8c6abf01e0dab1e27917
generic

dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5459e02707b27a964ae72e028d3ff72a3b687c4a
generic

dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f4b989d7d87381927b98d64492f8dcf979f57ab

Vendor Advisories for CVE-2026-93170(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 26× in last 7d / 73× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 06:46 UTCEG score recompute
  2. 2026-10-05 06:46 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 19:49 UTCGHSA enrichment
  5. 2026-10-04 08:53 UTCGHSA enrichment
  6. 2026-10-03 21:56 UTCEG score recompute
  7. 2026-10-03 21:56 UTCGHSA enrichment
  8. 2026-10-03 10:51 UTCGHSA enrichment
  9. 2026-10-02 23:54 UTCEG score recompute
  10. 2026-10-02 23:53 UTCGHSA enrichment
  11. 2026-10-02 12:46 UTCGHSA enrichment
  12. 2026-10-02 01:49 UTCGHSA enrichment
  13. 2026-10-01 14:45 UTCGHSA enrichment
  14. 2026-10-01 03:49 UTCGHSA enrichment
  15. 2026-09-30 16:52 UTCEG score recompute
  16. 2026-09-30 16:52 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 05:20 UTCGHSA enrichment
  19. 2026-09-29 18:21 UTCEG score recompute
  20. 2026-09-29 18:21 UTCGHSA enrichment
  21. 2026-09-29 06:42 UTCEG score recompute
  22. 2026-09-29 06:42 UTCGHSA enrichment
  23. 2026-09-28 19:46 UTCEG score recompute
  24. 2026-09-28 19:45 UTCGHSA enrichment
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 48 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 08:45 UTCGHSA enrichment
  3. 2026-09-27 21:48 UTCEG score recompute
  4. 2026-09-27 21:48 UTCGHSA enrichment
  5. 2026-09-27 13:49 UTCEPSS rescore
  6. 2026-09-27 10:49 UTCGHSA enrichment
  7. 2026-09-26 23:52 UTCEG score recompute
  8. 2026-09-26 23:52 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 12:55 UTCGHSA enrichment
  11. 2026-09-26 01:59 UTCEG score recompute
  12. 2026-09-26 01:58 UTCGHSA enrichment
  13. 2026-09-25 14:59 UTCGHSA enrichment
  14. 2026-09-25 04:00 UTCGHSA enrichment
  15. 2026-09-24 17:04 UTCEG score recompute
  16. 2026-09-24 17:04 UTCGHSA enrichment
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-24 06:07 UTCGHSA enrichment
  19. 2026-09-23 19:10 UTCEG score recompute
  20. 2026-09-23 19:10 UTCGHSA enrichment
  21. 2026-09-23 17:54 UTCEPSS rescore
  22. 2026-09-23 07:57 UTCGHSA enrichment
  23. 2026-09-22 21:00 UTCEG score recompute
  24. 2026-09-22 21:00 UTCGHSA enrichment
  25. 2026-09-22 16:01 UTCEPSS rescore
  26. 2026-09-22 10:03 UTCGHSA enrichment
  27. 2026-09-21 23:07 UTCEG score recompute
  28. 2026-09-21 23:06 UTCGHSA enrichment
  29. 2026-09-21 21:09 UTCEPSS rescore
  30. 2026-09-21 12:10 UTCGHSA enrichment
  31. 2026-09-21 01:13 UTCEG score recompute
  32. 2026-09-21 01:12 UTCGHSA enrichment
  33. 2026-09-20 20:16 UTCEPSS rescore
  34. 2026-09-20 14:12 UTCGHSA enrichment
  35. 2026-09-20 03:15 UTCGHSA enrichment
  36. 2026-09-19 16:19 UTCEG score recompute
  37. 2026-09-19 16:19 UTCGHSA enrichment
  38. 2026-09-19 05:23 UTCEG score recompute
  39. 2026-09-19 05:22 UTCGHSA enrichment
  40. 2026-09-18 19:28 UTCEPSS rescore
  41. 2026-09-18 18:26 UTCEG score recompute
  42. 2026-09-18 18:26 UTCGHSA enrichment
  43. 2026-09-18 18:00 UTCEG score recompute▲ 7.80
  44. 2026-09-18 18:00 UTCGHSA enrichment
  45. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  46. 2026-09-17 17:24 UTCNVD update
  47. 2026-09-17 16:20 UTCEG score recompute
  48. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93170?
CVE-2026-93170 is a high vulnerability published on September 17, 2026. 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…
When was CVE-2026-93170 disclosed?
CVE-2026-93170 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93170 actively exploited?
CVE-2026-93170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93170?
CVE-2026-93170 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93170?
No fix for CVE-2026-93170 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93170 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-93170

Explore →

Is Your Infrastructure Affected by CVE-2026-93170?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.