kunit: Fix Reference Count Leak in kfree_at_end
Summary
GSD-2021-1002115: kunit: fix reference count leak in kfree_at_end. Affects Kernel versions < bbdd158b40b66a9403391a517f24ef6613573446. 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 vulnerability affects the Kernel package in the Linux ecosystem. The Kernel package is responsible for providing the core functionality of the operating system. It manages the system's resources, including memory, processes, and hardware devices. The vulnerability in question involves a reference count leak in the kfree_at_end function.
Vulnerability Detail
The vulnerability in kfree_at_end results in a reference count leak. This means that when the function is called to free a resource, it fails to properly decrement the reference count associated with that resource. As a result, the resource may not be deallocated correctly, leading to potential memory leaks and resource exhaustion. The impact of this vulnerability can vary depending on the specific resource being leaked and the context in which it is used. Attackers may be able to exploit these memory leaks to cause denial of service conditions or potentially execute arbitrary code.
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
The vulnerability in kfree_at_end can lead to reference count leaks, potentially resulting in memory leaks and resource exhaustion. It is crucial to update the Linux Kernel package to version v5.14.15 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the specific resource being leaked and the context in which it is used. Attackers may be able to exploit these memory leaks to cause denial of service conditions or potentially execute arbitrary code.
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, and Vulert will analyze it for any open-source vulnerabilities, including this one.
Yes, a fix is available for this vulnerability. It is recommended to update the Linux Kernel package to version v5.14.15 or later.
At the time of this report, there are no known exploits for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
You can find more information about this vulnerability in the Open Source Vulnerability Database. The vulnerability ID is GSD-2021-1002115.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
