Memory Leak Vulnerability in tracing/histograms Package
Summary
GSD-2022-1004800: tracing/histograms: Fix memory leak problem. Affects Kernel versions >= 240dd5118a9e0454f280ffeae63f22bd14735733, < eb622d5580b9e2ff694f62da6410618bd73853cb. 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/histograms package is a component of the Linux Kernel, which is responsible for collecting and analyzing various system performance metrics. It provides functionality for creating and managing histograms, which are used to visualize and analyze data distribution. The package is an integral part of the kernel and is widely used in Linux-based systems.
Vulnerability Detail
The tracing/histograms package in the Linux Kernel is affected by a memory leak vulnerability. This vulnerability, identified as GSD-2022-1004800, allows an attacker to cause a memory leak by exploiting a flaw in the package's memory management mechanism. The vulnerability was introduced in version v4.19.149 of the Linux Kernel and was fixed in version v4.19.253. If left unpatched, this vulnerability can lead to memory exhaustion and potentially impact system stability and performance.
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 known workaround for this vulnerability. It is necessary to apply the patch or update the Linux Kernel to mitigate the risk of memory leaks.
Conclusion
The memory leak vulnerability in the tracing/histograms package of the Linux Kernel can lead to memory exhaustion and impact system stability and performance. It is crucial to update the Linux Kernel to version v4.19.253 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to memory exhaustion and potentially impact system stability and performance.
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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this memory leak vulnerability.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the patch or update the Linux Kernel to mitigate the risk.
No, this vulnerability requires local access to the system in order to exploit it.
There are no reported incidents related to this vulnerability at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
