CVE-2026-46255
Double Free in Linux Kernel FSL EDMA Driver
Publication date: 2026-06-03
Last updated on: 2026-06-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fsl | fsl_edma | * |
| freescale | fsl_edma | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is related to the Linux kernel's dmaengine driver for the Freescale EDMA (Enhanced Direct Memory Access) controller. Specifically, the issue occurs because the driver disables clocks manually in its remove function, even though these clocks are already managed and automatically cleaned up by the system. This results in warnings during driver removal, such as "edma_module already disabled" and related kernel warnings.
The root cause is that the clocks allocated and enabled with devm_clk_get_enabled() are automatically cleaned up, so manually disabling them again is unnecessary and causes these warnings. The fix removes the redundant clock disable calls in the driver's remove function.
How can this vulnerability impact me? :
This vulnerability primarily causes warning messages during the removal of the fsl_edma driver in the Linux kernel. These warnings indicate that clocks are being disabled multiple times unnecessarily.
While these warnings do not directly cause functional failures or security breaches, they can clutter system logs and potentially confuse system administrators or developers troubleshooting kernel or driver issues.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing warning messages related to clock disabling in the Linux kernel logs when the fsl_edma driver is removed.
- Check kernel logs for warnings such as 'edma_module already disabled' and 'edma_module already unprepared'.
- Use the command: dmesg | grep -i 'edma_module already disabled'
- Use the command: dmesg | grep -i 'edma_module already unprepared'
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation is to apply the fix that removes the unnecessary manual disabling of clocks in the fsl_edma_remove() function.
This fix prevents the warnings by relying on devm_clk_get_enabled() to automatically clean up the clocks without manual disable calls.
If you are not a developer, ensure your Linux kernel is updated to a version that includes this fix.