Refcount Leak in altera_tse_mdio_create in Kernel
Summary
GSD-2022-1003960: net: altera: Fix refcount leak in altera_tse_mdio_create. Affects Kernel versions >= bbd2190ce96d8fce031f0526c1f970b68adc9d1a, < 1fd12298a0e0ca23478c715e672ee64c85670584. 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 provides core functionality and acts as an interface between hardware and software. It manages system resources and facilitates communication between different software components. The altera_tse_mdio_create function in the Kernel is responsible for creating a Management Data Input/Output (MDIO) interface for Altera Triple-Speed Ethernet (TSE) devices. This interface allows the TSE device to communicate with external devices using the MDIO protocol.
Vulnerability Detail
The altera_tse_mdio_create function in the Kernel suffers from a refcount leak vulnerability. This vulnerability was introduced in version v3.15 of the Kernel by commit bbd2190ce96d8fce031f0526c1f970b68adc9d1a and is fixed in version v4.14.283 by commit 1fd12298a0e0ca23478c715e672ee64c85670584. The vulnerability occurs when the function fails to properly release a reference count, leading to a resource leak. An attacker could potentially exploit this vulnerability to exhaust system resources, resulting in a denial-of-service (DoS) condition or other unexpected behavior.
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
In conclusion, the altera_tse_mdio_create function in the Kernel is vulnerable to a refcount leak issue, which could result in a denial-of-service condition or other unexpected behavior. It is crucial to update the Kernel to version v4.14.283 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could potentially lead to a denial-of-service (DoS) condition or other unexpected behavior by exhausting system 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 and Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there are no known exploits for this vulnerability. However, it is important to patch your system to prevent any potential attacks.
No, this vulnerability requires local access to the affected system in order to exploit it.
No, there is no known workaround for this vulnerability. It is recommended to update the Kernel to the latest version.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.