Refcount Leak in axxia_boot_secondary in ARM Kernel
Summary
GSD-2022-1004619: ARM: Fix refcount leak in axxia_boot_secondary. Affects Kernel versions >= 1d22924e1c4e299337e86e290c02c3e3eb43b608, < 44a5b3a073e5aaa5720929dba95b2725eb32bb65. 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 ARM kernel is a crucial component of the Linux operating system that supports ARM-based processors. It provides essential functionality and interfaces for the proper functioning of ARM-based devices. The axxia_boot_secondary function is responsible for booting secondary CPUs in the Axxia platform. However, a refcount leak vulnerability has been identified in this function, potentially leading to resource exhaustion and system instability.
Vulnerability Detail
The refcount leak vulnerability in axxia_boot_secondary allows an attacker to cause a resource exhaustion condition by repeatedly triggering the affected function. By exploiting this vulnerability, an attacker could potentially crash the system or cause it to become unresponsive. The vulnerability was introduced in version v3.16 of the Linux Kernel and has been fixed in version v5.10.127. The fix involves commit 44a5b3a073e5aaa5720929dba95b2725eb32bb65.
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
As a workaround, users can disable the affected functionality by modifying the kernel configuration to exclude the Axxia platform or by preventing the axxia_boot_secondary function from being called. However, this workaround may not be feasible in all scenarios and is not a recommended long-term solution.
Conclusion
The refcount leak vulnerability in axxia_boot_secondary poses a risk of resource exhaustion and system instability. It is crucial to update the Linux Kernel to version v5.10.127 or later to mitigate this vulnerability. Users can also use Vulert's playground (https://vulert.com/scanner) to check if their system is affected and obtain real-time alerts for open-source vulnerabilities. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and system instability, potentially causing crashes or unresponsiveness.
You can use Vulert's playground (https://vulert.com/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 is no known public exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
As a temporary measure, you can disable the affected functionality or prevent the axxia_boot_secondary function from being called. However, it is strongly recommended to update the kernel to the fixed version as soon as possible.
You can refer to the Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) for more information about the fix. The vulnerability details can be found in the Cloud Security Alliance's GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1004xxx/GSD-2022-1004619.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
