CVE-2026-46255

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-03. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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().

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 3, 2026

Last Modified

July 22, 2026

Advisory Details (5)

Auto-updated Jun 16, 2026
No patch confirmed yet.
generic

dmaengine: fsl-edma: don't explicitly disable clocks in .remove() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bda244871179543dd3be7d093236cb33b2fb1765
generic

dmaengine: fsl-edma: don't explicitly disable clocks in .remove() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b84dba68c4823da452cec99a5d213571a65d06de
generic

dmaengine: fsl-edma: don't explicitly disable clocks in .remove() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68feac21bd4de7ae4faba05704c404861d991fcf
generic

dmaengine: fsl-edma: don't explicitly disable clocks in .remove() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/666c53e94c1d0bf0bdf14c49505ece9ddbe725bc
generic

dmaengine: fsl-edma: don't explicitly disable clocks in .remove() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/533d495f15e4c88ad5246c7f90ae026702e28d75

Vendor Advisories for CVE-2026-46255(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
linuxKernel @ 6.6.128—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1—

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 211 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 05:33 UTCEG score recompute
  3. 2026-09-14 05:33 UTCVendor advisory
  4. 2026-09-14 05:33 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 23:36 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 03:38 UTCEG score recompute
  22. 2026-08-25 03:38 UTCVendor advisory
  23. 2026-08-25 03:38 UTCGHSA enrichment
  24. 2026-08-23 12:48 UTCEG score recompute
  25. 2026-08-23 12:48 UTCVendor advisory
Show 75 more
  1. 2026-08-23 12:48 UTCGHSA enrichment
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 08:27 UTCEG score recompute
  5. 2026-08-21 08:27 UTCVendor advisory
  6. 2026-08-21 08:27 UTCGHSA enrichment
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 10:01 UTCEG score recompute
  9. 2026-08-20 10:01 UTCVendor advisory
  10. 2026-08-20 10:01 UTCGHSA enrichment
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 03:45 UTCEG score recompute
  15. 2026-08-17 03:45 UTCVendor advisory
  16. 2026-08-17 03:45 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:17 UTCEG score recompute
  19. 2026-08-16 02:17 UTCVendor advisory
  20. 2026-08-16 02:17 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 02:48 UTCEG score recompute
  23. 2026-08-15 02:48 UTCVendor advisory
  24. 2026-08-15 02:48 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-14 04:43 UTCEG score recompute
  27. 2026-08-14 04:43 UTCVendor advisory
  28. 2026-08-14 04:43 UTCGHSA enrichment
  29. 2026-08-13 22:00 UTCEPSS rescore
  30. 2026-08-13 06:39 UTCEG score recompute
  31. 2026-08-13 06:39 UTCVendor advisory
  32. 2026-08-13 06:39 UTCGHSA enrichment
  33. 2026-08-12 13:51 UTCEPSS rescore
  34. 2026-08-12 08:35 UTCVendor advisory
  35. 2026-08-12 08:35 UTCGHSA enrichment
  36. 2026-08-11 08:57 UTCEG score recompute
  37. 2026-08-11 08:57 UTCVendor advisory
  38. 2026-08-11 08:57 UTCGHSA enrichment
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-10 10:54 UTCEG score recompute
  41. 2026-08-10 10:54 UTCVendor advisory
  42. 2026-08-10 10:54 UTCGHSA enrichment
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-09 12:50 UTCEG score recompute
  45. 2026-08-09 12:50 UTCVendor advisory
  46. 2026-08-09 12:50 UTCGHSA enrichment
  47. 2026-08-08 16:37 UTCEPSS rescore
  48. 2026-08-08 14:46 UTCVendor advisory
  49. 2026-08-08 14:46 UTCGHSA enrichment
  50. 2026-08-07 16:40 UTCEG score recompute
  51. 2026-08-07 16:40 UTCVendor advisory
  52. 2026-08-07 16:40 UTCGHSA enrichment
  53. 2026-08-06 18:36 UTCEG score recompute
  54. 2026-08-06 18:36 UTCVendor advisory
  55. 2026-08-06 18:36 UTCGHSA enrichment
  56. 2026-08-06 13:47 UTCEPSS rescore
  57. 2026-08-05 20:32 UTCEG score recompute
  58. 2026-08-05 20:32 UTCVendor advisory
  59. 2026-08-05 20:32 UTCGHSA enrichment
  60. 2026-08-05 19:17 UTCEPSS rescore
  61. 2026-08-04 19:21 UTCEG score recompute
  62. 2026-08-04 19:21 UTCVendor advisory
  63. 2026-08-04 19:21 UTCGHSA enrichment
  64. 2026-08-04 15:10 UTCEPSS rescore
  65. 2026-08-03 15:43 UTCEG score recompute
  66. 2026-08-03 15:43 UTCVendor advisory
  67. 2026-08-03 15:43 UTCGHSA enrichment
  68. 2026-08-03 10:36 UTCEPSS rescore
  69. 2026-08-02 11:09 UTCEG score recompute
  70. 2026-08-02 11:09 UTCVendor advisory
  71. 2026-08-02 11:09 UTCGHSA enrichment
  72. 2026-08-02 02:27 UTCEPSS rescore
  73. 2026-08-01 13:05 UTCEG score recompute
  74. 2026-08-01 13:05 UTCVendor advisory
  75. 2026-08-01 13:05 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-46255?
CVE-2026-46255 is a medium vulnerability published on June 3, 2026. 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 devmclkget_enabled(), which automatically cleans these resources up, but these clocks are also…
When was CVE-2026-46255 disclosed?
CVE-2026-46255 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46255 actively exploited?
CVE-2026-46255 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-46255?
CVE-2026-46255 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46255?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46255, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46255

Explore →

Is Your Infrastructure Affected by CVE-2026-46255?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs