Memory Leak Vulnerability in tracing/histogram Package
Summary
GSD-2022-1000185: tracing/histogram: Fix a potential memory leak for kstrdup(). Affects Kernel versions >= d380dcde9a07ca5de4805dee11f58a98ec0ad6ff, < d71b06aa995007eafd247626d0669b9364c42ad7. 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 tracing/histogram package is a component of the Linux Kernel, which is responsible for collecting and analyzing various system events. It provides functionality for creating histograms to visualize the distribution of event data. The package is widely used in Linux-based systems for performance monitoring and debugging purposes. However, a vulnerability has been discovered in the package that can lead to a memory leak.
Vulnerability Detail
The vulnerability in the tracing/histogram package is related to the improper handling of memory allocation and deallocation. Specifically, when using the kstrdup() function, there is a potential memory leak if the allocation fails. This can result in the consumption of system resources and potentially lead to performance degradation or even system instability. The vulnerability was introduced in version v5.6 of the Linux Kernel and has been fixed in version v5.10.96.
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 →
Workaround
There is no specific workaround mentioned for this vulnerability. The recommended approach is to apply the fix by updating the Linux Kernel to the latest version.
Conclusion
The memory leak vulnerability in the tracing/histogram package of the Linux Kernel can lead to resource consumption and potential system instability. It is crucial to update the Linux Kernel to version v5.10.96 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in a memory leak, which can consume system resources and potentially lead to performance degradation or system instability.
You can use the Vulert Playground at Vulert 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 and alert you if the vulnerability is present.
At the time of this report, there is no known exploit for this vulnerability. However, it is still important to apply the fix to prevent any potential memory leaks.
No, this vulnerability does not have a remote exploitation vector. It requires local access to the system.
This vulnerability specifically affects the tracing/histogram package in the Linux Kernel. There are no known dependencies or other packages impacted.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
