CVE-2026-93169: Linux kernel · dmaengine: zynqmp_dma: fix race between runtime PM and device removal
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in aec7cf9a5bd89047c58d5648bfce0b1bd19ba7d5 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:19 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in aec7cf9a5bd89047c58d5648bfce0b1bd19ba7d5, 516ba2d8b7aac4238f9fcbd58579c43c71b9b695, 32f69e6c95b59f9cfc649ebf352a204d23ba93d7
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to aec7cf9a5bd89047c58d5648bfce0b1bd19ba7d5, 516ba2d8b7aac4238f9fcbd58579c43c71b9b695 or 32f69e6c95b59f9cfc649ebf352a204d23ba93d7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel versions identified by the fixed commit hashes. Users should update to a kernel version that includes these fixes to prevent the race condition. No additional mitigation is required beyond applying the official fix.
Description
A race condition vulnerability in the Linux kernel's dmaengine driver for zynqmp_dma was fixed. The issue involved a race between runtime power management (PM) and device removal, where runtime PM was disabled too late in the removal process, potentially causing unsafe runtime PM transitions.