CVE-2025-71191: dmaengine: at_hdmac: fix device leak on of_dma_xlate()
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: at_hdmac: fix device leak on of_dma_xlate()
Make sure to drop the reference taken when looking up the DMA platform
device during of_dma_xlate() when releasing channel resources.
Note that commit 3832b78b3ec2 ("dmaengine: at_hdmac: add missing
put_device() call in at_dma_xlate()") fixed the leak in a couple of
error paths but the reference is still leaking on successful allocation.
Security readout for executives and security teams
Plain-English summary
CVE-2025-71191 is a Linux kernel resource-leak bug in the at_hdmac DMA driver. The kernel may keep an extra device reference after successful DMA channel allocation. The public record does not provide a CVSS score or exploitation evidence. Business impact is most likely stability or availability risk on systems that use this driver.
Executive priority
Handle through normal kernel and vendor patch management, with higher priority for embedded or industrial systems where downtime is costly. There is no public evidence here of active exploitation, but the bug can affect kernel resource management and long-running system reliability.
Technical view
The fix ensures a device reference acquired during of_dma_xlate() is released when channel resources are freed. A prior change fixed some error paths, but successful allocation still leaked the reference. Affected entries list Linux kernel versions including 3.10 through 6.19, with stable kernel commits referenced as fixes.
Likely exposure
Exposure appears limited to Linux systems running affected kernels where the at_hdmac DMA engine driver and relevant device-tree DMA translation path are used. This is more relevant to embedded, appliance, and industrial Linux deployments than general-purpose servers without this hardware path.
Exploitation context
The source bundle shows no CISA KEV listing and no cited evidence of active exploitation. The described flaw is a kernel reference leak, not a direct remote code execution issue. Practical impact likely depends on whether repeated channel allocation can trigger resource exhaustion or device lifecycle problems.
Researcher notes
Evidence is limited to the CVE description, Linux stable commits, and Siemens advisory links. No CVSS, CWE, exploitability assessment, or product-specific Siemens affected details are included in the provided bundle. Avoid assuming broad exposure without confirming at_hdmac use and vendor backport status.
Mitigation direction
Check vendor kernel advisories for fixed builds containing the referenced stable commits.
Update affected Linux kernels through your distribution, device vendor, or kernel maintenance channel.
For Siemens-managed environments, review the two Siemens ProductCERT advisories linked in the record.
Prioritize embedded and industrial assets using at_hdmac-capable hardware.
If no update is available, ask the vendor for supported mitigation guidance.
Validation and detection
Inventory Linux kernel versions across affected appliances and embedded systems.
Check whether the at_hdmac driver is built, loaded, or enabled in kernel configuration.
Confirm whether relevant device-tree DMA mappings use this driver path.
Verify installed kernels include one of the referenced stable fix commits or vendor backports.
Track vendor advisories for product-specific affected status and update availability.
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-71191 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:42 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.