CVE-2025-71186: dmaengine: stm32: dmamux: fix device leak on route allocation
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: stm32: dmamux: fix device leak on route allocation
Make sure to drop the reference taken when looking up the DMA mux
platform device during route allocation.
Note that holding a reference to a device does not prevent its driver
data from going away so there is no point in keeping the reference.
Security readout for executives and security teams
Plain-English summary
CVE-2025-71186 is a Linux kernel fix for a resource leak in the STM32 DMA multiplexer driver. It appears most relevant to embedded or industrial Linux devices using STM32 hardware. Public sources do not provide CVSS, a clear impact statement, or evidence of active exploitation.
Executive priority
Treat as a targeted maintenance issue, not an emergency, unless critical embedded or Siemens-managed industrial systems use affected STM32 Linux kernels. Prioritize verification and normal kernel update cycles, with faster action for safety- or availability-sensitive devices.
Technical view
The Linux kernel patch fixes a device reference leak in dmaengine/stm32/dmamux route allocation. The code took a reference while looking up the DMA mux platform device and failed to drop it. The upstream notes say holding the reference does not protect driver data, so keeping it is unnecessary.
Likely exposure
Exposure is most likely on Linux-based embedded systems using the STM32 DMAMUX dmaengine driver. Standard enterprise servers are unlikely to be exposed unless they include this driver and relevant hardware. Siemens advisories reference this CVE, so affected Siemens product owners should review those notices directly.
Exploitation context
No provided source reports active exploitation, public exploit availability, or KEV listing. The available information describes a kernel resource-management bug, not a remotely exploitable path. Practical risk depends on whether affected hardware, driver configuration, and vulnerable kernel code are present.
Researcher notes
The record lacks CVSS, CWE, and detailed impact analysis. The affected-version data is ambiguous in the provided bundle. Researchers should inspect the linked stable commits and downstream vendor advisories before assigning operational severity or declaring product exposure.
Mitigation direction
Update to a vendor-supported kernel containing the referenced upstream stable fix.
Check Linux distribution advisories for packaged kernel availability.
For Siemens products, review SSA-253495 and SSA-019113 for product-specific guidance.
Prioritize embedded and industrial Linux assets using STM32 hardware.
Validation and detection
Inventory Linux kernels on embedded and industrial assets.
Confirm whether STM32 DMAMUX dmaengine support is built or loaded.
Compare kernel source or package changelogs against the referenced stable commits.
Check Siemens advisories for named products and fixed versions.
Document unaffected systems where STM32 DMAMUX hardware or driver is absent.
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-71186 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
1ADP providers
10Source 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.
Jan 31, 2026, 11:41 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.