Memory Leak Vulnerability in phy: mdio Package
Summary
GSD-2021-1001525: phy: mdio: fix memory leak. Affects Kernel versions >= 46abc02175b3c246dd5141d878f565a8725060c9, < f4f502a04ee1e543825af78f47eb7785015cd9f6. 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 phy: mdio package is a component of the Linux Kernel, which is responsible for managing the Media Independent Interface (MII) bus for Ethernet PHY devices. It provides the necessary functions for communication between the Ethernet controller and the PHY devices. The vulnerability in this package relates to a memory leak issue.
Vulnerability Detail
The memory leak vulnerability in phy: mdio can lead to the gradual consumption of system memory resources. When the package is used to communicate with PHY devices, it fails to release allocated memory properly, resulting in memory leaks. Over time, this can cause a depletion of available memory, leading to system instability and potential denial-of-service (DoS) conditions. The vulnerability was introduced in version v2.6.28 of the Linux Kernel and has been fixed in version v4.14.251.
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 →
Conclusion
The memory leak vulnerability in phy: mdio can have serious consequences for system stability and availability. It is crucial to update the Linux Kernel to the fixed version to mitigate the risk of memory leaks and potential denial-of-service conditions. For further assistance or support in addressing this vulnerability, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The memory leak vulnerability in phy: mdio can lead to system instability and potential denial-of-service (DoS) conditions due to the gradual consumption of system memory resources.
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 to the playground, and it will analyze and alert you in real-time if the vulnerability is present.
Currently, there are no known workarounds for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
There is no information available regarding exploitation of this vulnerability in the wild.
You can find more information about this vulnerability in the vulnerability database maintained by the Cloud Security Alliance. The specific vulnerability ID is GSD-2021-1001525. https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1001xxx/GSD-2021-1001525.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
