CVE-2026-93168

published 17 Sep 2026 · updated 20 Nov 2026

dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f786e7b3adbf3bd14964a1cedf9d55b6ad91dcd7, Kernel 2ba67aa183a3ce174d534425b67eda84f6e3c896, Kernel 4237b5cc181a17f5a2a797655c1ce2c64e01c550 and 8 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=9495f2648287029fb5545c34a0fa318426ebe84c <f786e7b3adbf3bd14964a1cedf9d55b6ad91dcd7, >=9495f2648287029fb5545c34a0fa318426ebe84c <2ba67aa183a3ce174d534425b67eda84f6e3c896, >=9495f2648287029fb5545c34a0fa318426ebe84c <4237b5cc181a17f5a2a797655c1ce2c64e01c550, >=9495f2648287029fb5545c34a0fa318426ebe84c <8b5654d317277e6e505c23f8fa7e415237fefc7f, >=9495f2648287029fb5545c34a0fa318426ebe84c <aa99c4d1d63bbc26a5fc4c667d89b2595743c19d, >=9495f2648287029fb5545c34a0fa318426ebe84c <c30a26d4987a01e619449bf170f584c007e07d75, =4.6f786e7b3adbf3bd14964a1cedf9d55b6ad91dcd7, 2ba67aa183a3ce174d534425b67eda84f6e3c896, 4237b5cc181a17f5a2a797655c1ce2c64e01c550, 8b5654d317277e6e505c23f8fa7e415237fefc7f, aa99c4d1d63bbc26a5fc4c667d89b2595743c19d, c30a26d4987a01e619449bf170f584c007e07d75
linux-kernel: Kernel>=6.13.0 <6.18.57, >=6.19.0 <7.2.6, >=6.2.0 <6.6.160, >=6.7.0 <6.12.114, >=4.6.0 <6.1.1916.18.57, 7.2.6, 6.6.160, 6.12.114, 6.1.191

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-93168 severity on Zeptric[![CVE-2026-93168](https://zeptric.io/badge/cve/CVE-2026-93168.svg)](https://zeptric.io/cve/CVE-2026-93168)