Refcount Leak in axxia_boot_secondary in ARM Kernel

Kernel Updated 02 Oct 2025

Summary

31/07/2022
N/A
No i
Unrated
Not published

GSD-2022-1004735: ARM: Fix refcount leak in axxia_boot_secondary. Affects Kernel versions >= 1d22924e1c4e299337e86e290c02c3e3eb43b608, < 29ca9c4efacccdc15104a8d4bf10b5183fc92840. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The ARM kernel is a crucial component of the Linux operating system that supports ARM-based processors. It provides the necessary functionality for managing hardware resources, scheduling tasks, and facilitating communication between software and hardware components. The axxia_boot_secondary function is a part of the ARM kernel that handles the booting of secondary CPUs in multi-core systems. This function is responsible for initializing and starting the execution of additional CPU cores. However, a refcount leak vulnerability has been identified in the axxia_boot_secondary function, which could lead to resource exhaustion and potential system instability.

Vulnerability Detail

The refcount leak vulnerability in axxia_boot_secondary arises from a failure to properly manage reference counts when booting secondary CPUs. When a secondary CPU is booted, the reference count for the corresponding CPU is incremented. However, if an error occurs during the boot process, such as a failure to allocate resources, the reference count is not properly decremented, leading to a leak. Over time, this can result in the exhaustion of system resources and potential instability. An attacker with local access to the affected system could potentially exploit this vulnerability to cause a denial-of-service condition or escalate their privileges.

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 avoid the potential impact of this vulnerability by disabling the booting of secondary CPUs. This can be achieved by modifying the system's configuration or boot parameters to prevent the initialization of additional CPU cores. However, this workaround may limit the system's performance and utilization of available hardware resources.

Conclusion

The refcount leak vulnerability in axxia_boot_secondary poses a risk of resource exhaustion and potential system instability. It is crucial to update the Linux Kernel to version v5.4.202 or later to fix this vulnerability. Alternatively, users can apply the provided workaround of disabling the booting of secondary CPUs, although this may impact system performance. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to resource exhaustion and potential system instability. An attacker with local access to the affected system could potentially cause a denial-of-service condition or escalate their privileges.

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, and Vulert will analyze it for any open-source vulnerabilities, including this one.

Yes, a patch is available in the Linux Kernel version v5.4.202. By updating to this version or a later one, you can fix the vulnerability and ensure proper resource management during the booting of secondary CPUs.

As a temporary workaround, you can disable the booting of secondary CPUs to avoid the potential impact of this vulnerability. However, this may limit the system's performance and utilization of available hardware resources.

There are no known instances of this vulnerability being exploited in the wild. However, it is still important to apply the necessary patches or updates to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback