FKIE_CVE-2026-46255

Vulnerability from fkie_nvd - Published: 2026-06-03 18:16 - Updated: 2026-06-03 18:16
Severity
Summary
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().
Impacted products
Vendor Product Version

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: fsl-edma: don\u0027t explicitly disable clocks in .remove()\n\nThe clocks in fsl_edma_engine::muxclk are allocated and enabled with\ndevm_clk_get_enabled(), which automatically cleans these resources up,\nbut these clocks are also manually disabled in fsl_edma_remove(). This\ncauses warnings on driver removal for each clock:\n\n        edma_module already disabled\n        WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1200 clk_core_disable+0x198/0x1c8\n        [...]\n        Call trace:\n         clk_core_disable+0x198/0x1c8 (P)\n         clk_disable+0x34/0x58\n         fsl_edma_remove+0x74/0xe8 [fsl_edma]\n         [...]\n        ---[ end trace 0000000000000000 ]---\n        edma_module already unprepared\n        WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1059 clk_core_unprepare+0x1f8/0x220\n        [...]\n        Call trace:\n         clk_core_unprepare+0x1f8/0x220 (P)\n         clk_unprepare+0x34/0x58\n         fsl_edma_remove+0x7c/0xe8 [fsl_edma]\n         [...]\n        ---[ end trace 0000000000000000 ]---\n\nFix these warnings by removing the unnecessary fsl_disable_clocks() call\nin fsl_edma_remove()."
    }
  ],
  "id": "CVE-2026-46255",
  "lastModified": "2026-06-03T18:16:26.463",
  "metrics": {},
  "published": "2026-06-03T18:16:26.463",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/533d495f15e4c88ad5246c7f90ae026702e28d75"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/666c53e94c1d0bf0bdf14c49505ece9ddbe725bc"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/68feac21bd4de7ae4faba05704c404861d991fcf"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/b84dba68c4823da452cec99a5d213571a65d06de"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/bda244871179543dd3be7d093236cb33b2fb1765"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…