A missing cleanup in the DMA engine driver for OMAP devices causes the dma_pool created during device registration to remain allocated when the probe fails. The leak means that repeated failures can gradually consume kernel memory, potentially destabilizing the system or leading to a denial-of-service if the kernel runs out of memory. The flaw originates from improper resource management when dma_async_device_register() or of_dma_controller_register() returns an error.

The issue affects any Linux kernel that includes the DMA engine implementation for OMAP devices and has not been updated to the patch that adds dma_pool_destroy() in the failure paths. Specific kernel releases are not listed, so all affected kernels without the mitigation should be considered vulnerable.

The EPSS score is reported as below 1 %, indicating a very low probability that the vulnerability will be actively exploited. It is not listed in the CISA KEV catalog. The attack vector is local to the kernel, as the leak occurs during driver probe on boot or module load. An attacker with sufficient privilege to trigger re‑probe conditions could repeatedly exhaust kernel memory, but the lack of a public exploit and low exploit probability reduce the immediate risk. Nonetheless, the impact on availability warrants timely patching.