Memory Leak in mkiss_close in Kernel
Summary
GSD-2021-1001070: net: hamradio: fix memory leak in mkiss_close. Affects Kernel versions >= 815f62bf742718458ba822a7e1f51f285eb997f2, < f4de2b43d13b7cf3ced9310e371b90c836dbd7cd. 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 crucial component of the Linux operating system that manages system resources and provides an interface for applications to interact with the hardware. It is responsible for tasks such as process management, memory management, and device drivers. The mkiss_close function in the hamradio module of the Kernel is vulnerable to a memory leak issue.
Vulnerability Detail
The vulnerability in mkiss_close can lead to a memory leak, which occurs when memory is allocated but not properly deallocated, resulting in a gradual reduction of available memory. This can eventually lead to system instability or crashes. The issue was introduced in version v2.6.14 of the Linux Kernel and has been fixed in version v5.12.13. 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 →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
The memory leak vulnerability in mkiss_close in the Kernel can potentially lead to system instability or crashes. It is recommended to update the Linux Kernel to version v5.12.13 or later to fix this vulnerability. Regularly updating the Kernel is important to ensure the latest security patches and bug fixes are applied. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially lead to system instability or crashes due to memory leaks.
You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It analyzes manifest files like package-lock.json to identify open-source vulnerabilities.
There is no known exploit for this vulnerability at the moment.
It is recommended to update the Kernel to the latest version to mitigate the risk. However, if updating is not feasible, you can consider implementing additional security measures such as network segmentation and access controls to minimize the potential impact.
You can refer to the vulnerability details in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1001xxx/GSD-2021-1001070.json) for more information.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
