Skip to main content

Linux Kernel CVE-2026-46255

| EUVDEUVD-2026-34117 MEDIUM
2026-06-03 Linux GHSA-wm23-vr7p-8cm6
Information Disclosure Linux Red Hat Suse
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE
MEDIUM
qualitative
Red Hat
5.5 LOW
qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jun 09, 2026 - 20:26 vuln.today
CVSS changed
Jun 09, 2026 - 20:22 NVD
5.5 (MEDIUM)
Patch available
Jun 03, 2026 - 19:01 EUVD
CVE Published
Jun 03, 2026 - 15:49 nvd
MEDIUM 5.5
CVE Published
Jun 03, 2026 - 15:49 nvd
UNKNOWN (no severity yet)

DescriptionCVE.org

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

AnalysisAI

Double-disable of managed clocks in the Linux kernel's fsl-edma (Freescale/NXP eDMA) DMA engine driver triggers kernel WARN_ON warnings during driver removal, causing an availability impact on affected systems. The bug originates from commit a9903de3aa16731846bf924342eca44bdabe9be6, where clocks allocated via devm_clk_get_enabled() - which automatically handles teardown - are also manually disabled in fsl_edma_remove(), resulting in a 'already disabled/unprepared' warning for each clock. No public exploit has been identified at time of analysis, and EPSS is 0.02% (5th percentile), reflecting the low likelihood of targeted exploitation of this kernel quality defect.

Technical ContextAI

The fsl-edma driver (drivers/dma/fsl-edma.c) manages DMA channels for NXP/Freescale SoCs and uses the Linux devres (device-managed resources) subsystem via devm_clk_get_enabled() to allocate and enable multiplexer clocks stored in fsl_edma_engine::muxclk. The devres framework guarantees automatic resource release - including clock disable and unprepare - when the device is detached or the driver removed. A redundant manual call to fsl_disable_clocks() in fsl_edma_remove() duplicates this teardown, causing clk_core_disable() and clk_core_unprepare() to be invoked on already-torn-down clocks. The root cause is a double-free/double-release antipattern against the kernel clock subsystem, resulting in WARN_ON assertions at clk.c:1200 and clk.c:1059. CWE is not assigned, but this most closely resembles a use-after-free or double-release defect in resource lifecycle management. CPE data identifies the affected product as cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* across multiple stable branches.

RemediationAI

Upgrade to a patched Linux kernel version. Vendor-released patches are available across five stable branches: 6.6.128 (commit 533d495f15e4c88ad5246c7f90ae026702e28d75), 6.12.75 (commit bda244871179543dd3be7d093236cb33b2fb1765), 6.18.14 (commit 68feac21bd4de7ae4faba05704c404861d991fcf), 6.19.4 (commit b84dba68c4823da452cec99a5d213571a65d06de), and mainline 7.0 (commit 666c53e94c1d0bf0bdf14c49505ece9ddbe725bc). Patch commits are accessible at https://git.kernel.org/stable/c/ with the respective commit hashes. As a workaround on unpatched systems where fsl-edma module unloading is not operationally required, preventing unload of the fsl-edma module (e.g., via modprobe blacklist or setting the module as built-in) will prevent the double-disable code path from executing; however, this does not eliminate the underlying defect and may interfere with hot-plug or power management workflows on affected SoCs. Downstream distributions (Red Hat, Debian, Ubuntu, etc.) should be monitored for inclusion of these stable-branch fixes in their kernel packages.

Same technique Information Disclosure

View all
CVE-2013-2251 CRITICAL POC
9.8
CVE-2017-5638 CRITICAL POC
9.8
CVE-2025-24813 CRITICAL POC
9.8
CVE-2015-1701 HIGH POC
7.8
CVE-2017-0147 HIGH POC
7.5
CVE-2014-6324 HIGH POC
8.8
CVE-2023-7028 CRITICAL POC
10.0
CVE-2017-0213 HIGH POC
7.3

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Performance Computing 15 SP7 Not-Affected

Share

CVE-2026-46255 vulnerability details – vuln.today
Back

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy