Refcount Leak in ill_acc_of_setup() in mips: ralink
Summary
GSD-2022-1002195: mips: ralink: fix a refcount leak in ill_acc_of_setup(). Affects Kernel versions < 060a485df4ec1183d543317511cb4caa43468b5d. 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 vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for applications to interact with the hardware. The specific vulnerability, known as a refcount leak, occurs in the ill_acc_of_setup() function in the mips: ralink code. This function is responsible for setting up the ill_acc_of device. A refcount leak can lead to memory leaks and potential resource exhaustion.
Vulnerability Detail
The refcount leak vulnerability in ill_acc_of_setup() can be exploited by an attacker to cause memory leaks and potentially exhaust system resources. This can result in denial of service (DoS) attacks or other security issues. The vulnerability has been fixed in Linux Kernel version v5.4.189 by commit 060a485df4ec1183d543317511cb4caa43468b5d. It is important to update to this version or later to mitigate the vulnerability.
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 refcount leak vulnerability in ill_acc_of_setup() in mips: ralink has been fixed in Linux Kernel version v5.4.189. It is important to update to this version or later to mitigate the vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory leaks and potential resource exhaustion, which can result in denial of service (DoS) attacks or other security issues.
You can check the version of the Linux Kernel installed on your system. If it is earlier than v5.4.189, your system may be affected. You can also use tools like Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability.
At the time of this report, there are no known exploits for this vulnerability. However, it is important to update to the fixed version to prevent potential exploitation.
No specific workaround has been provided for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel.
You can find more information about the fix in the commit 060a485df4ec1183d543317511cb4caa43468b5d in the Linux Kernel repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
