Vulnerability in arch/arm64 package: Fix topology initialization for core scheduling

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001017: arch/arm64: Fix topology initialization for core scheduling. Affects Kernel versions >= 9edeaea1bc452372718837ed2ba775811baf1ba1, < c78a1b2d0bff678570c8dc9f14035606f5e5257d. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The arch/arm64 package is a component of the Linux Kernel, which is responsible for supporting the ARMv8-A architecture on 64-bit ARM processors. It provides the necessary functionality for running the Linux operating system on ARM-based devices. The package includes various modules and drivers specific to the ARM64 architecture, ensuring proper hardware support and system operation. However, a vulnerability has been identified in the package related to topology initialization for core scheduling.

Vulnerability Detail

The vulnerability in the arch/arm64 package affects the initialization of topology information used for core scheduling. Core scheduling is a feature that allows the operating system to balance the workload across CPU cores efficiently. The issue arises from a flaw in the code that handles the initialization process, leading to incorrect topology information being set. This can result in suboptimal core scheduling decisions, potentially impacting system performance and resource allocation. The vulnerability was introduced in version v5.14 of the Linux Kernel and has been fixed in version v5.17.3.

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. The recommended course of action is to apply the fix by updating the Linux Kernel to the patched version.

Conclusion

In conclusion, the arch/arm64 package in the Linux Kernel is vulnerable to a flaw in topology initialization for core scheduling. This can result in suboptimal core scheduling decisions, potentially impacting system performance. To mitigate this vulnerability, it is recommended to update the Linux Kernel to version v5.17.3 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to suboptimal core scheduling decisions, potentially affecting system performance and resource allocation.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and the tool will analyze it for any vulnerable packages.

At the time of this report, no known exploits for this vulnerability have been disclosed. However, it is always recommended to apply security patches promptly to mitigate any potential risks.

The primary solution is to update the Linux Kernel to the patched version. However, if updating is not feasible in the short term, you can consider implementing additional security measures, such as network segmentation and access controls, to reduce the potential impact of the vulnerability.

For more detailed information about this vulnerability, including technical details and the specific code changes made to fix it, you can refer to the source link provided in the vulnerability details section of this report.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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