CVE-2026-93168dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout Currently when calling xilinx_dma_poll_timeout with delay_us=0 and a condition that is never fulfilled, the CPU busy-waits for prolonged time and the timeout triggers only with a massive delay causing a CPU stall. This happens due to a huge underestimation of wall clock time in poll_timeout_us_atomic. Commit 7349a69cf312 ("iopoll: Do not use timekeeping in read_poll_timeout_atomic()") changed the behavior to no longer use ktime_get at the expense of underestimation of wall clock time which appears to be very large for delay_us=0. Instead of timing out after approximately XILINX_DMA_LOOP_COUNT microseconds, the timeout takes XILINX_DMA_LOOP_COUNT * 1000 * (time that the overhead of the for loop in poll_timeout_us_atomic takes) which is in the range of several minutes for XILINX_DMA_LOOP_COUNT=1000000. Fix this by using a non-zero value for delay_us. Use delay_us=10 to keep the delay in the hot path of starting DMA transfers minimal but still avoid CPU stalls in case of unexpected hardware failures. One-off measurement with delay_us=0 causes the cpu to busy wait around 7 minutes in the timeout case. After applying this patch with delay_us=10 the measured timeout was 1053428 microseconds which is roughly equivalent to the expected 1000000 microseconds specified in XILINX_DMA_LOOP_COUNT. Add a constant XILINX_DMA_POLL_DELAY_US for delay_us value.
Timeline
ID reserved
By Linux
Published
- 43 days later
· 43 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 9495f2648287029fb5545c34a0fa318426ebe84c – < 4237b5cc181a17f5a2a797655c1ce2c64e01c550
- affected 9495f2648287029fb5545c34a0fa318426ebe84c – < 2ba67aa183a3ce174d534425b67eda84f6e3c896
- affected 9495f2648287029fb5545c34a0fa318426ebe84c – < c30a26d4987a01e619449bf170f584c007e07d75
- affected 9495f2648287029fb5545c34a0fa318426ebe84c – < f786e7b3adbf3bd14964a1cedf9d55b6ad91dcd7
- affected 9495f2648287029fb5545c34a0fa318426ebe84c – < 8b5654d317277e6e505c23f8fa7e415237fefc7f
- affected 9495f2648287029fb5545c34a0fa318426ebe84c – < aa99c4d1d63bbc26a5fc4c667d89b2595743c19d
- affected 4.6
- unaffected < 4.6
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/4237b5cc181a17f5a2a797655c1ce2c64e01c550 (opens in a new tab)
- https://git.kernel.org/stable/c/2ba67aa183a3ce174d534425b67eda84f6e3c896 (opens in a new tab)
- https://git.kernel.org/stable/c/c30a26d4987a01e619449bf170f584c007e07d75 (opens in a new tab)
- https://git.kernel.org/stable/c/f786e7b3adbf3bd14964a1cedf9d55b6ad91dcd7 (opens in a new tab)
- https://git.kernel.org/stable/c/8b5654d317277e6e505c23f8fa7e415237fefc7f (opens in a new tab)
- https://git.kernel.org/stable/c/aa99c4d1d63bbc26a5fc4c667d89b2595743c19d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-82276 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93168)Record last updated .