Memory Leak in __mdiobus_register in Kernel
Summary
GSD-2021-1001922: net: mdiobus: Fix memory leak in __mdiobus_register. Affects Kernel versions < fd2400dd4f1b8bd7a309b1b424d9e0d188151b01. 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 critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functions for device drivers, file systems, and process management. The __mdiobus_register function is part of the mdiobus subsystem, which handles management of Ethernet PHY devices. This vulnerability in __mdiobus_register can lead to a memory leak, causing a gradual depletion of available memory resources.
Vulnerability Detail
The vulnerability in __mdiobus_register arises from a memory leak issue. When the function is called to register an Ethernet PHY device, it fails to release allocated memory in certain scenarios. This can result in a gradual accumulation of memory leaks over time, potentially leading to system instability or denial of service if memory resources are exhausted. The vulnerability has been identified and fixed in the Linux Kernel version v4.4.290 by commit fd2400dd4f1b8bd7a309b1b424d9e0d188151b01.
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
As this vulnerability has been fixed in the Linux Kernel, there is no specific workaround available. It is recommended to apply the fix by updating the Kernel to the patched version.
Conclusion
The memory leak vulnerability in __mdiobus_register in the Kernel can lead to gradual depletion of memory resources, potentially causing system instability or denial of service. It is crucial to update the Linux Kernel to version v4.4.290 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a memory leak, gradually depleting available memory resources. This can result in system instability or denial of service if memory resources are exhausted.
You can use tools like Vulert (https://vulert.com) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix promptly to mitigate any potential risks.
This vulnerability does not have a direct remote exploitation vector. However, if an attacker gains access to the affected system, they may be able to trigger the vulnerability and exploit it to exhaust memory resources.
If updating the Kernel is not immediately feasible, it is recommended to closely monitor system resources and take appropriate action if memory usage starts to exhibit abnormal behavior. Additionally, implementing strict access controls and network security measures can help reduce the risk of unauthorized access to the system.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
