Vulnerability · Published Jun 3, 2026 · Assigned by Linux
CVE-2026-46255dmaengine: fsl-edma: don't explicitly disable clocks in .remove()
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 1% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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().
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:13 | linux | 6.12.85-1 | DEBIAN-CVE-2026-46255 |
| Debian:14 | linux | 6.18.14-1 | DEBIAN-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux | 6.8.0-134.134 | UBUNTU-CVE-2026-46255 |
| Ubuntu:25.10 | linux | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1060.63 | UBUNTU-CVE-2026-46255 |
| Ubuntu:25.10 | linux-aws | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1060.63~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1063.71 | UBUNTU-CVE-2026-46255 |
| Ubuntu:25.10 | linux-azure | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1063.71~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1062.69 | UBUNTU-CVE-2026-46255 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1062.69~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1063.69 | UBUNTU-CVE-2026-46255 |
| Ubuntu:25.10 | linux-gcp | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1063.69~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1058.64 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1045.48 | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-136.136~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1060.61 | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1060.61~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-134.134.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-134.134.1~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1058.61 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1058.61~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1058.61.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1029.30 | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1057.58 | UBUNTU-CVE-2026-46255 |
| Ubuntu:25.10 | linux-oracle | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1057.58~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1060.64 | UBUNTU-CVE-2026-46255 |
| Ubuntu:25.10 | linux-raspi | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:25.10 | linux-realtime | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:25.10 | linux-riscv | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-134.134~22.04.1 | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-46255 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1032.33 | UBUNTU-CVE-2026-46255 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | a9903de3aa16731846bf924342eca44bdabe9be6 – before 533d495f15e4c88ad5246c7f90ae026702e28d75a9903de3aa16731846bf924342eca44bdabe9be6 – before 68feac21bd4de7ae4faba05704c404861d991fcfa9903de3aa16731846bf924342eca44bdabe9be6 – before bda244871179543dd3be7d093236cb33b2fb1765a9903de3aa16731846bf924342eca44bdabe9be6 – before b84dba68c4823da452cec99a5d213571a65d06dea9903de3aa16731846bf924342eca44bdabe9be6 – before 666c53e94c1d0bf0bdf14c49505ece9ddbe725bc |
| Linux | Linux | 6.6 |
References
- https://git.kernel.org/stable/c/533d495f15e4c88ad5246c7f90ae026702e28d75
- https://git.kernel.org/stable/c/68feac21bd4de7ae4faba05704c404861d991fcf
- https://git.kernel.org/stable/c/bda244871179543dd3be7d093236cb33b2fb1765
- https://git.kernel.org/stable/c/b84dba68c4823da452cec99a5d213571a65d06de
- https://git.kernel.org/stable/c/666c53e94c1d0bf0bdf14c49505ece9ddbe725bc