LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35983: bounds: Use the right number of bits for power-of-two CONFIG_NR_CPUS

In the Linux kernel, the following vulnerability has been resolved: bounds: Use the right number of bits for power-of-two CONFIG_NR_CPUS bits_per() rounds up to the next power of two when passed a power of two. This causes crashes on some machines and configurations.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-35983 is a Linux kernel defect that can crash some machines when CPU-count bounds are calculated incorrectly for power-of-two CONFIG_NR_CPUS values. The public bundle does not provide CVSS, CWE, CPEs, or evidence of active exploitation, so business urgency depends on where vulnerable kernel builds are deployed.

Executive priority

Handle through normal kernel maintenance unless affected systems are stability-critical or already showing unexplained crashes. Escalate priority for industrial, appliance, or high-availability Linux deployments where downtime has material business impact.

Technical view

The issue is in Linux kernel bounds handling: bits_per() rounds up incorrectly when given a power-of-two CONFIG_NR_CPUS value, leading to crashes on some configurations. The record points to multiple stable kernel commits and Linux stable versions, but the supplied data does not define exact vulnerable ranges or exploitation prerequisites.

Likely exposure

Exposure appears limited to Linux systems running kernel builds that include the faulty bounds logic and relevant CONFIG_NR_CPUS configurations. The source bundle names Linux only, lists no CPEs, and includes stable commits plus versions 5.4.274, 5.10.215, 5.15.154, 6.1.84, 6.6.24, and 6.8.3.

Exploitation context

The supplied sources do not indicate active exploitation, and KEV is false. The described impact is crash behavior on some machines and configurations, not a demonstrated remote attack path. Treat this primarily as an availability and operational stability risk unless vendor advisories state otherwise.

Researcher notes

The record lacks CVSS, CWE, CPEs, exact vulnerable ranges, and exploitability detail. Analysis should stay anchored to kernel stable commits and vendor advisories. Do not assume remote exploitability or privilege impact from the supplied evidence.

Mitigation direction

  • Update Linux kernels through supported distribution or vendor channels.
  • Review Debian LTS guidance if using Debian-based systems.
  • Review Siemens advisories if operating listed Siemens products.
  • Prioritize systems with high or unusual CONFIG_NR_CPUS settings.
  • Monitor vendor advisories for precise fixed package versions.

Validation and detection

  • Inventory running kernel versions and vendor package revisions.
  • Confirm whether systems use power-of-two CONFIG_NR_CPUS values.
  • Map kernel builds to the referenced stable fixes or vendor advisories.
  • Review crash logs for kernel failures matching this defect.
  • Document exceptions where vendor guidance is unavailable.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-35983 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd6077e0d38b4953c863d0db4a5b3f41d21e0d546, 83a2275f9d3230c761014b1467888b1ef469be74, d2a7a81088c6abe778b0a93a7eeb79487a943818, 428ca0000f0abd5c99354c52a36becf2b815ca21, b46c822f8b555b9513df44047b0e72c06720df62, cf778fff03be1ee88c49b72959650147573c3301, f2d5dcb48f7ba9e3ff249d58fc1fa963d374e66a, b2e1b090a590d41abe647eadb6bf2a5dc47b63abunaffected
LinuxLinux5.4.274, 5.10.215, 5.15.154, 6.1.84, 6.6.24, 6.8.3unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.