CVE-2025-71186: Linux kernel · dmaengine: stm32: dmamux: fix device leak on route allocation
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in dd6e4943889fb354efa3f700e42739da9bddb6ef : update Linux kernel when convenient.
Data as of 10 Nov 2026, 13:03 UTC
Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- Patch
- Available – fixed in dd6e4943889fb354efa3f700e42739da9bddb6ef, 6393da54dcb3488c080a183c4182ddec71ba8d7f, 3ef52d31cce8ba816739085a61efe07b63c6cf27 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 31 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
The vulnerability has been fixed in multiple Linux kernel commits as listed in the established facts. Users should update their Linux kernel to a version that includes these fixes to remediate the issue. No additional mitigation steps are required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's dmaengine subsystem for STM32 devices involving the DMA multiplexer (dmamux) has been fixed. The issue was a device reference leak during route allocation, where references taken when looking up the DMA mux platform device were not properly dropped. This could lead to resource leaks but does not prevent driver data from being freed.
References
- git.kernel.org/stable/c/3b42020e6790a5e19b36c187ed5b488a5716f97f (opens in a new tab)
- git.kernel.org/stable/c/6393da54dcb3488c080a183c4182ddec71ba8d7f (opens in a new tab)
- git.kernel.org/stable/c/1dda2a32303df0091896b01a9d09070d61fa344c (opens in a new tab)
- git.kernel.org/stable/c/1a179ac01ff3993ab97e33cc77c316ed7415cda1 (opens in a new tab)
- git.kernel.org/stable/c/2fb10259d4efb4367787b5ae9c94192e8a91c648 (opens in a new tab)
- git.kernel.org/stable/c/3ef52d31cce8ba816739085a61efe07b63c6cf27 (opens in a new tab)
- git.kernel.org/stable/c/dd6e4943889fb354efa3f700e42739da9bddb6ef (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-253495.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)