Refcount Leak in ti_dra7_xbar_route_allocate in Kernel
Summary
GSD-2022-1004588: dmaengine: ti: Fix refcount leak in ti_dra7_xbar_route_allocate. Affects Kernel versions >= ec9bfa1e1a796ef7acc2e55917c9b8be5a79e70e, < 37147e22cd8dfc0412495cb361708836157a4486. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Kernel is a fundamental component of the Linux operating system that manages core system functions, including hardware communication and resource allocation. It provides an interface between the hardware and software layers, allowing applications to interact with the underlying system. The ti_dra7_xbar_route_allocate function in the Kernel's dmaengine subsystem is responsible for allocating routes in the TI DRA7 XBAR. This subsystem enables data transfers between different devices in the system. However, a vulnerability has been identified in this function that can lead to a refcount leak.
Vulnerability Detail
The refcount leak vulnerability in ti_dra7_xbar_route_allocate allows an attacker to cause a memory leak by repeatedly allocating routes without releasing them. This can result in a depletion of available memory resources, leading to system instability or denial of service. The vulnerability was introduced in version v4.5 of the Linux Kernel and has been fixed in version v5.10.130. The fix involves commit 37147e22cd8dfc0412495cb361708836157a4486. It is important to note that the impact and attack plausibility of this vulnerability have not been proven.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Conclusion
The refcount leak vulnerability in ti_dra7_xbar_route_allocate in the Kernel can lead to memory leaks and potential system instability or denial of service. It is crucial to update the Linux Kernel to version v5.10.130 or later to fix this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a memory leak, potentially causing system instability or denial of service.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze the dependencies for any known vulnerabilities.
No specific workaround has been provided for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel.
The remote exploitability of this vulnerability has not been determined. Further analysis is required to assess the potential attack vectors.
There are no known instances of this vulnerability being exploited in the wild. However, it is always recommended to apply security updates to mitigate potential risks.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
