CVE-2022-48656: dmaengine: ti: k3-udma-private: Fix refcount leak bug in of_xudma_dev_get()
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: ti: k3-udma-private: Fix refcount leak bug in of_xudma_dev_get()
We should call of_node_put() for the reference returned by
of_parse_phandle() in fail path or when it is not used anymore.
Here we only need to move the of_node_put() before the check.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel resource-management bug in the TI K3 UDMA DMA engine driver. A device-tree reference may not be released on some paths, causing a reference count leak. Business urgency appears limited unless affected Linux kernels run on hardware using this driver; the sources provide no CVSS, impact details, or active exploitation evidence.
Executive priority
Handle through normal kernel patch management unless affected TI K3-based systems are business-critical. There is insufficient evidence for emergency response, but unmanaged embedded kernels may need focused review.
Technical view
The issue is in of_xudma_dev_get() within k3-udma-private. A reference returned by of_parse_phandle() was not always released with of_node_put(). The kernel fix moves of_node_put() before a check so the reference is dropped when no longer needed, including failure handling.
Likely exposure
Exposure is mainly Linux systems using affected kernels with the TI K3 UDMA private DMA engine path. The supplied data names Linux kernel versions but does not provide a complete product matrix, distribution mapping, or affected hardware inventory.
Exploitation context
The source bundle does not report active exploitation, public exploit activity, KEV listing, or a practical attack path. Treat this as a kernel reliability/resource-management issue unless vendor guidance provides stronger impact evidence.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. No CVSS, CWE, exploit status, or detailed impact analysis is provided. Avoid extrapolating beyond a refcount leak in the TI K3 UDMA driver path.
Mitigation direction
Check kernel vendor advisories for affected distribution packages and fixed builds.
Prioritize systems using TI K3 UDMA-capable hardware or custom kernels.
Update to a vendor kernel containing the referenced stable fixes.
If no fixed package exists, track vendor guidance rather than applying ad hoc patches.
Validation and detection
Inventory Linux kernel versions across embedded and server fleets.
Identify systems with TI K3 UDMA DMA engine support enabled.
Compare running kernels against vendor advisories and referenced stable commits.
Confirm the deployed kernel package includes the of_node_put() refcount fix.
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-2022-48656 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.