System crashes via power-of-two CPU bit overcount
Published May 20, 2024 · Updated May 23, 2026
Improper input validation in Linux kernel bounds generation allows local users to crash affected Linux-based systems. kernel/bounds.c passes a power-of-two CONFIG_NR_CPUS value to bits_per(), which rounds up and generates an oversized NR_CPUS_BITS value. Exploitation requires local low-privileged access and an affected kernel built with SMP and a power-of-two CPU limit; confidentiality and integrity effects are not reported.
Summary
What happened
Improper input validation in Linux kernel bounds generation allows local users to crash affected Linux-based systems. kernel/bounds.c passes a power-of-two CONFIG_NR_CPUS value to bits_per(), which rounds up and generates an oversized NR_CPUS_BITS value. Exploitation requires local low-privileged access and an affected kernel built with SMP and a power-of-two CPU limit; confidentiality and integrity effects are not reported.
The record
- CVE
- CVE-2024-35983
- Published
- May 20, 2024
- Updated
- May 23, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-20, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=0 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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