Memory Leak Vulnerability in tracing/histogram Package
Summary
GSD-2022-1000149: tracing/histogram: Fix a potential memory leak for kstrdup(). Affects Kernel versions >= 38b67e60b6b582e81f9db1b2e7176cbbfbd3e574, < 8a8878ebb596281f50fc0b9a6e1f23f0d7f154e8. 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 utilizes the kstrdup() function for duplicating strings, which is vulnerable to a memory leak issue.
Vulnerability Detail
The vulnerability in the tracing/histogram package arises from a potential memory leak in the kstrdup() function. This function is used to allocate memory and duplicate strings. However, if an error occurs during the duplication process, the allocated memory is not properly freed, resulting in a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, leading to a denial-of-service condition. The vulnerability was introduced in version v5.4.19 of the Linux Kernel and has been fixed in version v5.4.176.
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.
Conclusion
In conclusion, the tracing/histogram package in the Linux Kernel is vulnerable to a memory leak issue in the kstrdup() function. This vulnerability can potentially lead to a denial-of-service condition. It is recommended to update the Linux Kernel to version v5.4.176 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could potentially lead to a denial-of-service condition by exhausting system memory resources.
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 provide real-time alerts for open-source vulnerabilities.
There is no known exploit for this vulnerability at the moment. However, it is important to apply the recommended fix to prevent any potential exploitation.
No, the recommended fix for this vulnerability is to update the Linux Kernel to version v5.4.176 or later.
You can find more information about this vulnerability in the GSD-2022-1000149.json file available in the GSD database repository at https://github.com/cloudsecurityalliance/gsd-database.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
