Linux Kernel EUVD-2026-25453

Exploitation requires: (1) local account access to the target system with at least low-privilege shell access (PR:L per CVSS); (2) the spi-dw-dma kernel module must be loaded, which requires the system to have DesignWare SPI DMA hardware present and in use; (3) the attacker must be able to induce an error condition during an SPI DMA transaction such that the driver's error-handling path is reached while the current message pointer is NULL. Systems without DesignWare SPI IP hardware, or where the spi-dw-dma module is not loaded, are entirely unaffected. General-purpose x86 servers, cloud instances, and desktop Linux systems will not have this driver active. Exploitation is limited by the combination of required local access and hardware specificity - remote unauthenticated exploitation is not possible given AV:L in the CVSS vector.

The CVSS 3.1 score of 5.5 (Medium) with vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H correctly characterises this as a local denial-of-service requiring low-privilege access, with no confidentiality or integrity impact. The EPSS score of 0.02% at the 5th percentile is consistent with a kernel driver stability fix that attracts no meaningful exploitation interest from the threat community. There is no CISA KEV listing and no public exploit code has been identified. The hardware dependency - the DesignWare SPI DMA IP block - substantially narrows the realistic attack surface to embedded Linux systems, industrial controllers, and SoC-based platforms rather than general-purpose servers or desktops. The combination of local access requirement, hardware specificity, low EPSS, and lack of KEV listing places this firmly in the category of a kernel reliability fix with low security priority for most organisations. Teams maintaining embedded or industrial Linux images should patch as part of normal maintenance cycles rather than treating this as an emergency.

A local user with a standard shell account on an embedded Linux system - such as an industrial gateway or SoC development board - using DesignWare SPI DMA hardware deliberately induces an error condition during an SPI DMA transfer, for example by interfering with a connected SPI peripheral or writing invalid data through a kernel interface. When the driver's error handler attempts to log the failure, it dereferences the NULL current-message pointer, triggering an immediate kernel panic and system crash. No public exploit code exists for this vulnerability.