Memory Leak in net: hamradio: fix memory leak in mkiss_close
Summary
GSD-2021-1000924: net: hamradio: fix memory leak in mkiss_close. Affects Kernel versions >= 815f62bf742718458ba822a7e1f51f285eb997f2, < a49cbb762ef20655f5c91abdc13658b0af5e159d. 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 net package in the Linux Kernel is responsible for handling network-related operations. It provides various protocols and drivers for different network functionalities. One of the protocols supported is hamradio, which is used for amateur radio communication. The mkiss_close function in the hamradio module is responsible for closing a Multi-drop KISS (MKISS) interface. However, a memory leak vulnerability has been identified in this function.
Vulnerability Detail
The memory leak vulnerability in mkiss_close allows an attacker to cause a continuous allocation of memory resources without proper deallocation. This can lead to a depletion of available memory, resulting in system instability or denial of service. The vulnerability was introduced in version v2.6.14 of the Linux Kernel and is fixed in version v5.4.128. The specific commit that addresses this issue is a49cbb762ef20655f5c91abdc13658b0af5e159d.
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 recommended to apply the fix by updating the Linux Kernel.
Conclusion
The memory leak vulnerability in the net: hamradio module's mkiss_close function can lead to memory exhaustion and system instability. It is crucial to update the Linux Kernel to version v5.4.128 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 lead to memory exhaustion, potentially causing system instability or denial of service.
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 tool will analyze it for any known vulnerabilities.
There is no information available regarding active exploitation of this vulnerability at the moment.
There are no reported incidents related to this vulnerability at the moment.
You can refer to the vulnerability database entry at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000924.json for more details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
