CVE-2025-38479: dmaengine: fsl-edma: free irq correctly in remove path
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: fsl-edma: free irq correctly in remove path
Add fsl_edma->txirq/errirq check to avoid below warning because no
errirq at i.MX9 platform. Otherwise there will be kernel dump:
WARNING: CPU: 0 PID: 11 at kernel/irq/devres.c:144 devm_free_irq+0x74/0x80
Modules linked in:
CPU: 0 UID: 0 PID: 11 Comm: kworker/u8:0 Not tainted 6.12.0-rc7#18
Hardware name: NXP i.MX93 11X11 EVK board (DT)
Workqueue: events_unbound deferred_probe_work_func
pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : devm_free_irq+0x74/0x80
lr : devm_free_irq+0x48/0x80
Call trace:
devm_free_irq+0x74/0x80 (P)
devm_free_irq+0x48/0x80 (L)
fsl_edma_remove+0xc4/0xc8
platform_remove+0x28/0x44
device_remove+0x4c/0x80
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver cleanup bug in the Freescale/NXP eDMA driver. On platforms without an error IRQ, such as i.MX9, device removal can trigger a kernel warning and dump. The source bundle does not show remote exploitation, active exploitation, or business-impact scoring.
Executive priority
Handle through normal kernel maintenance unless affected embedded platforms are business-critical or showing kernel warnings. There is no source-backed evidence of active exploitation or remote compromise, but unresolved kernel dumps can affect operational stability.
Technical view
The fsl-edma dmaengine remove path called devm_free_irq without checking whether txirq or errirq existed. On i.MX9, missing errirq caused a devm_free_irq warning during deferred probe or remove. Kernel stable commits add IRQ presence checks before freeing.
Likely exposure
Exposure appears limited to Linux kernels using the fsl-edma DMA engine, especially NXP i.MX9 or similar embedded platforms. The bundle lists Linux kernel versions and stable commits but does not provide distro package mappings or deployment prevalence.
Exploitation context
CISA KEV status is false in the bundle. No cited source reports exploitation in the wild, exploit code, a remote attack path, or privilege requirements. Treat this as an operational kernel reliability issue unless vendor advisories state otherwise.
Researcher notes
Evidence is narrow: the description includes a warning stack trace and the fix theme, but no CVSS, CWE, attack vector, or distro mapping. Validation should focus on affected hardware, kernel branch, and presence of stable backports.
Mitigation direction
Update to a kernel containing the referenced stable fixes or vendor backport.
Check NXP, Linux distribution, and device vendor advisories for packaged fixes.
Prioritize embedded systems using i.MX9 or fsl-edma hardware.
Avoid assuming unrelated Linux systems are exposed without driver and hardware evidence.
Validation and detection
Inventory kernel versions on devices using Freescale/NXP eDMA hardware.
Confirm whether the fsl-edma driver is present and active.
Check vendor kernel changelogs for the referenced stable commit IDs.
Review kernel logs for devm_free_irq warnings during probe or device removal.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38479 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Apr 18, 2025, 07:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.