CVE-2026-46255 Details
Description
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().
A problem has been identified in the Linux kernel's fsl-edma DMA engine driver related to improper clock management during the removal of the driver. The issue arises because the clocks are allocated and enabled using a function that automatically handles resource cleanup. However, they are also manually disabled in the driver's removal function, leading to warnings about the clocks being already disabled. This mismanagement can cause unnecessary complications when the driver is unloaded.
The issue can be fixed by removing the manual clock disabling from the fsl-edma removal function, allowing the automatic cleanup process to manage the clocks appropriately.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/533d495f15e4c88ad5246c7f90ae026702e28d75 | kernel.org | Patch |
| https://git.kernel.org/stable/c/666c53e94c1d0bf0bdf14c49505ece9ddbe725bc | kernel.org | Patch |
| https://git.kernel.org/stable/c/68feac21bd4de7ae4faba05704c404861d991fcf | kernel.org | Patch |
| https://git.kernel.org/stable/c/b84dba68c4823da452cec99a5d213571a65d06de | kernel.org | Patch |
| https://git.kernel.org/stable/c/bda244871179543dd3be7d093236cb33b2fb1765 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.6, < 6.6.128 >= 6.7, < 6.12.75 >= 6.13, < 6.18.14 >= 6.19, < 6.19.4 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 22, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 9, 2026 | Initial Analysis | [email protected] |
| Jun 3, 2026 | New CVE Received | kernel.org |