Refcount Leak in axxia_boot_secondary in Kernel
Summary
GSD-2022-1004245: ARM: Fix refcount leak in axxia_boot_secondary. Affects Kernel versions >= 1d22924e1c4e299337e86e290c02c3e3eb43b608, < 3c19fe3f04f4f4e7a2b722c2fd3c98356fc1d72b. 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 manages system resources and facilitates communication between hardware and software. It is responsible for tasks such as process management, memory management, and device drivers. The axxia_boot_secondary function in the ARM architecture is used to boot secondary CPUs. However, a refcount leak vulnerability has been identified in this function.
Vulnerability Detail
The refcount leak vulnerability in axxia_boot_secondary allows an attacker to cause a reference count leak, leading to a resource exhaustion condition. By repeatedly triggering this vulnerability, an attacker can exhaust system resources, potentially resulting in a denial-of-service (DoS) scenario. The vulnerability was introduced in version v3.16 of the Linux Kernel and has been fixed in version v5.18.8.
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
No specific workaround has been provided for this vulnerability.
Conclusion
The refcount leak vulnerability in axxia_boot_secondary in the Kernel can lead to a denial-of-service (DoS) scenario by exhausting system resources. It is recommended to update the Linux Kernel to version v5.18.8 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service (DoS) scenario 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 to the playground and it will alert you if the vulnerability is present.
At the time of this report, no known exploits for this vulnerability have been disclosed.
The recommended mitigation is to update the Linux Kernel to version v5.18.8 or later, which includes the fix for this vulnerability.
You can find more information about this vulnerability in the GSD-2022-1004245 entry of the GSD database at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1004xxx/GSD-2022-1004245.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
