Memory Leak Vulnerability in Kernel: net: mdiobus
Summary
GSD-2021-1002055: net: mdiobus: Fix memory leak in __mdiobus_register. Affects Kernel versions < 3a0dc2e35a5d6546b1db87fe985582dadc64fe7b. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. The net: mdiobus module is responsible for managing the Media Independent Interface (MII) bus, which is used for communication between network devices and the network controller. This vulnerability affects the __mdiobus_register function in the net: mdiobus module, leading to a memory leak. A memory leak occurs when memory is allocated but not properly deallocated, resulting in a gradual depletion of available memory resources.
Vulnerability Detail
The vulnerability in __mdiobus_register can be exploited by an attacker to exhaust system memory resources, potentially leading to a denial-of-service (DoS) condition. By repeatedly triggering the memory leak, an attacker could cause the system to become unresponsive or crash. The vulnerability has been fixed in Linux Kernel version v5.10.76 by commit 3a0dc2e35a5d6546b1db87fe985582dadc64fe7b.
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 essential to apply the fix by updating the Linux Kernel to the patched version.
Conclusion
The memory leak vulnerability in the net: mdiobus module of the Linux Kernel can lead to a denial-of-service condition by exhausting system memory resources. It is crucial to update the Kernel to version v5.10.76 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, potentially causing a denial-of-service (DoS) condition by exhausting system memory resources.
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 to the playground, and it will analyze the dependencies and alert you if any known vulnerabilities are present.
At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the fix as soon as possible to mitigate the risk.
This vulnerability can potentially be exploited remotely if the affected system is accessible over the network. By sending specially crafted network packets, an attacker could trigger the memory leak and cause a denial-of-service condition.
The only known solution to fix this vulnerability is to update the Linux Kernel to the patched version. Applying the fix ensures that the memory leak is resolved and system resources are properly managed.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
