Executive brief
A technical issue was identified in the Linux kernel's fsl-edma driver, which manages Direct Memory Access (DMA) for certain Freescale processors. When the driver is removed or stopped, it incorrectly attempts to shut down system clocks that are already being managed automatically. While this does not typically lead to a security breach or data loss, it causes system warnings and could potentially impact the stability of the driver removal process.
Technical details
A double-disable vulnerability exists in the dmaengine: fsl-edma driver. The clocks in fsl_edma_engine::muxclk are allocated and enabled using devm_clk_get_enabled(), which provides managed resource cleanup. However, the fsl_edma_remove() function also explicitly calls fsl_disable_clocks(), leading to a 'clocks already disabled' warning and a kernel stack trace during driver detachment. This is a functional bug rather than a security exploit, though it indicates improper resource management. The fix involves removing the redundant manual clock disablement call in the .remove() path.
Affected products
- Linux Linux Kernel fsl-edma driver
Timeline
- 2026-01-13: other: Patch submitted by developer
- 2026-06-03: advisory: CVE published by NVD
References
- https://git.kernel.org/stable/c/533d495f15e4c88ad5246c7f90ae026702e28d75
- https://git.kernel.org/stable/c/666c53e94c1d0bf0bdf14c49505ece9ddbe725bc
- https://git.kernel.org/stable/c/68feac21bd4de7ae4faba05704c404861d991fcf
- https://git.kernel.org/stable/c/b84dba68c4823da452cec99a5d213571a65d06de
- https://git.kernel.org/stable/c/bda244871179543dd3be7d093236cb33b2fb1765