Linux Kernel Vulnerability: CONFIG_CPUMASK_OFFSTACK Warning in cpuinfo

linux Updated 02 Oct 2025

Summary

18/06/2025
N/A
Yes i
Unrated
Not published

CVE-2022-50223: In the Linux kernel, the following vulnerability has been resolved: LoongArch: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected, cpu_max_bits_warn(... Affects linux versions < 6.0.2-1. Fixed in 6.0.2-1. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux kernel is the core component of many operating systems, responsible for managing hardware resources and providing essential services to software applications. It is known for its stability, performance, and flexibility, supporting a wide range of hardware architectures. This vulnerability specifically affects the LoongArch architecture, where a warning is generated when displaying CPU information in /proc/cpuinfo due to a misconfiguration in the handling of CPU masks.

Vulnerability Detail

In the Linux kernel, when both CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are enabled, a runtime warning occurs during the execution of the cpu_max_bits_warn() function while displaying /proc/cpuinfo. This warning indicates a potential issue with CPU mask handling, which could lead to incorrect CPU information being presented to users or applications. The warning is triggered because the code iterates over CPUs using a static limit (NR_CPUS) instead of the dynamic runtime limit (nr_cpu_ids), which can lead to inconsistencies and confusion.

How To Fix

Minimum fixed version

6.0.2-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the patch by updating the package to the latest version.

Conclusion

The vulnerability identified in the Linux kernel regarding the CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS settings highlights the importance of proper CPU mask handling. By updating to the patched version, users can eliminate the warning and ensure accurate CPU information is displayed. Regular monitoring and updates are essential for maintaining system integrity.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

The primary impact is the generation of a runtime warning when displaying CPU information, which may lead to confusion or misinterpretation of CPU capabilities.

While it does not pose a direct security threat, it can affect system diagnostics and monitoring by providing inaccurate CPU information.

You can check your system's kernel version and configuration settings. Additionally, using tools like Vulert can help monitor and alert for such vulnerabilities.

If an immediate update is not possible, ensure that you are aware of the warning and monitor your system for any unusual behavior related to CPU management.

Detailed information can be found in the CVE database and through the Linux kernel mailing lists or documentation.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

6.0.2-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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