Refcount Leak in altera_tse_mdio_create in Kernel
Summary
GSD-2022-1003714: net: altera: Fix refcount leak in altera_tse_mdio_create. Affects Kernel versions >= bbd2190ce96d8fce031f0526c1f970b68adc9d1a, < 8174acbef87b8dd8bf3731eba2a5af1ac857e239. 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 crucial component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functions and services for the proper functioning of the system. The altera_tse_mdio_create function is part of the network subsystem in the Kernel and is responsible for creating an MDIO bus for the Altera Triple-Speed Ethernet (TSE) driver. The MDIO bus is used for communication between Ethernet PHYs and the Ethernet MAC controller. This vulnerability affects the altera_tse_mdio_create function, leading to a refcount leak.
Vulnerability Detail
The vulnerability in the altera_tse_mdio_create function results in a refcount leak. This means that the reference count for a resource is not properly managed, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, causing a denial-of-service (DoS) condition. The vulnerability was introduced in version v3.15 of the Linux Kernel and is fixed in version v5.4.198. The impact and attack plausibility of this vulnerability have not been proven.
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 specific workaround mentioned for this vulnerability. The recommended approach is to update the Linux Kernel to the fixed version.
Conclusion
The refcount leak vulnerability in the altera_tse_mdio_create function of the Kernel can potentially lead to a denial-of-service (DoS) condition. It is crucial to update the Linux Kernel to version v5.4.198 or later to fix this vulnerability and ensure the system's security. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is a potential denial-of-service (DoS) condition due to memory exhaustion.
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 alert you in real-time if the vulnerability is present.
No, there is no known exploit for this vulnerability at the moment.
No, the recommended approach is to update the Linux Kernel to the fixed version to mitigate this vulnerability.
There are no specific system requirements mentioned for this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
