Refcount Leak in altera_tse_mdio_create in Kernel
Summary
GSD-2022-1002600: net: altera: Fix refcount leak in altera_tse_mdio_create. Affects Kernel versions >= bbd2190ce96d8fce031f0526c1f970b68adc9d1a, < 4f850fe0a32c3f1e19b76996a3b1ca32637a14de. 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 functionalities and manages system resources. It is responsible for facilitating communication between hardware and software components. The altera_tse_mdio_create function in the Kernel's net: altera module is used to create 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's net: altera module has a refcount leak vulnerability. This vulnerability occurs when the function fails to properly release a reference count on the MDIO interface, leading to a resource leak. An attacker could potentially exploit this vulnerability to exhaust system resources, resulting in a denial-of-service (DoS) condition. The vulnerability was introduced in version v3.15 of the Linux Kernel and has been fixed in version v5.18.4.
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 necessary to update the Linux Kernel to the fixed version.
Conclusion
The refcount leak vulnerability in the altera_tse_mdio_create function of the Kernel's net: altera module can lead to a denial-of-service (DoS) condition. It is crucial to update the Linux Kernel to version v5.18.4 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 by exhausting system 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 and the Vulert Playground will analyze it for open-source vulnerabilities, including this one.
Yes, a patch for this vulnerability is available in version v5.18.4 of the Linux Kernel.
No, this vulnerability requires local access to the system.
There are no known instances of this vulnerability being exploited in the wild.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
