CVE-2026-46255: dmaengine: fsl-edma: don't explicitly disable clocks in .remove()
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: fsl-edma: don't explicitly disable clocks in .remove()
The clocks in fsledmaengine::muxclk are allocated and enabled with devmclkgetenabled(), which automatically cleans these resources up, but these clocks are also manually disabled in fsledmaremove(). This causes warnings on driver removal for each clock:
edmamodule already disabled WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1200 clkcoredisable+0x198/0x1c8 [...] Call trace: clkcoredisable+0x198/0x1c8 (P) clkdisable+0x34/0x58 fsledmaremove+0x74/0xe8 [fsledma] [...] ---[ end trace 0000000000000000 ]--- edmamodule already unprepared WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1059 clkcoreunprepare+0x1f8/0x220 [...] Call trace: clkcoreunprepare+0x1f8/0x220 (P) clkunprepare+0x34/0x58 fsledmaremove+0x7c/0xe8 [fsledma] [...] ---[ end trace 0000000000000000 ]---
Fix these warnings by removing the unnecessary fsldisableclocks() call in fsledmaremove().
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Fix the warnings by removing the unnecessary fsl_disable_clocks() call in fsl_edma_remove(), since muxclk is already disabled/unprepared by devm_clk_get_enabled() cleanup.
Linux kernel fsl-edma driver fsl_edma_remove() clock handling = remove explicit fsl_disable_clocks()/manual clock disable call(s) during driver removal
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46255?
CVE-2026-46255 has a risk rating of 2, indicating it is a low severity vulnerability.
How do I fix CVE-2026-46255?
To resolve CVE-2026-46255, ensure that the clocks are managed appropriately without explicit disablement in the .remove() function.
Which versions of the Linux kernel are affected by CVE-2026-46255?
CVE-2026-46255 affects specific versions of the Linux kernel that utilize the fsl-edma driver for DMA engine.
What is the impact of CVE-2026-46255 on system performance?
The impact of CVE-2026-46255 is minimal, as it relates to resource management rather than direct system functionality.
Is CVE-2026-46255 a critical vulnerability?
No, CVE-2026-46255 is not considered critical but should be addressed to maintain best practices in resource handling.