PT-2026-46018 · Linux · Linux
Published
2026-06-03
·
Updated
2026-06-03
·
CVE-2026-46255
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: fsl-edma: don't explicitly disable clocks in .remove()
The clocks in fsl edma engine::muxclk are allocated and enabled with
devm clk get enabled(), which automatically cleans these resources up,
but these clocks are also manually disabled in fsl edma remove(). This
causes warnings on driver removal for each clock:
edma module already disabled
WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1200 clk core disable+0x198/0x1c8
[...]
Call trace:
clk core disable+0x198/0x1c8 (P)
clk disable+0x34/0x58
fsl edma remove+0x74/0xe8 [fsl edma]
[...]
---[ end trace 0000000000000000 ]---
edma module already unprepared
WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1059 clk core unprepare+0x1f8/0x220
[...]
Call trace:
clk core unprepare+0x1f8/0x220 (P)
clk unprepare+0x34/0x58
fsl edma remove+0x7c/0xe8 [fsl edma]
[...]
---[ end trace 0000000000000000 ]---Fix these warnings by removing the unnecessary fsl disable clocks() call
in fsl edma remove().
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux