Runtime warning via out-of-range CPU iteration
Published Dec 27, 2024 · Updated May 11, 2026
Out-of-range CPU iteration in the Linux kernel allows local users to trigger a runtime warning by reading /proc/cpuinfo. The SH show_cpuinfo path iterates to the compile-time NR_CPUS limit, causing cpu_max_bits_warn() when the runtime nr_cpu_ids mask is smaller. The condition requires CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS; it normally emits diagnostics, but a panic-on-warning policy causes a kernel panic.
Summary
What happened
Out-of-range CPU iteration in the Linux kernel allows local users to trigger a runtime warning by reading /proc/cpuinfo. The SH show_cpuinfo path iterates to the compile-time NR_CPUS limit, causing cpu_max_bits_warn() when the runtime nr_cpu_ids mask is smaller. The condition requires CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS; it normally emits diagnostics, but a panic-on-warning policy causes a kernel panic.
The record
- CVE
- CVE-2022-49034
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <09faf32c682ea4a547200b8b9e04d8b3c8e84b55
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2b6b8e011fab680a223b5e07a3c64774156ec6fe
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <39373f6f89f52770a5405d30dddd08a27d097872
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3c891f7c6a4e90bb1199497552f24b26e46383bc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <701e32900683378d93693fec15d133e2c5f7ada2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <77755dc95ff2f9a3e473acc1e039f498629949ea
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8fbb57eabfc8ae67115cb47f904614c99d626a89
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e2b91997db286a5dd3cca6d5d9c20004851f22eb
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f8f26cf69003a37ffa947631fc0e6fe6daee624a
- Affected versionversion=2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo