LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26883: bpf: Fix stackmap overflow check on 32-bit arches

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix stackmap overflow check on 32-bit arches The stackmap code relies on roundup_pow_of_two() to compute the number of hash buckets, and contains an overflow check by checking if the resulting value is 0. However, on 32-bit arches, the roundup code itself can overflow by doing a 32-bit left-shift of an unsigned long value, which is undefined behaviour, so it is not guaranteed to truncate neatly. This was triggered by syzbot on the DEVMAP_HASH type, which contains the same check, copied from the hashtab code. The commit in the fixes tag actually attempted to fix this, but the fix did not account for the UB, so the fix only works on CPUs where an overflow does result in a neat truncation to zero, which is not guaranteed. Checking the value before rounding does not have this problem.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26883 is a Linux kernel BPF bug affecting 32-bit architectures. A size calculation intended to prevent overflow could itself overflow unpredictably. The sources confirm kernel fixes exist, but do not provide CVSS, CWE, or a concrete impact statement.

Executive priority

Track and remediate through routine kernel patch management, with higher priority for 32-bit Linux systems running untrusted workloads. Current urgency is limited by missing severity and exploitation evidence.

Technical view

The BPF stackmap code used roundup_pow_of_two() to size hash buckets and then checked for zero. On 32-bit architectures, the rounding operation could invoke undefined behavior through a left shift before the overflow check. The fix checks the input value before rounding.

Likely exposure

Likely exposure is limited to affected Linux kernel versions on 32-bit architectures, especially where BPF map functionality is available. The supplied sources do not establish exposure for 64-bit-only systems or identify specific distributions beyond referenced Debian LTS advisories and vendor notices.

Exploitation context

The CVE says syzbot triggered the issue, but the bundle does not show public exploitation, weaponized exploit availability, or CISA KEV listing. Treat active exploitation as unconfirmed.

Researcher notes

The key issue is undefined behavior before the overflow check, not a missing check after rounding. The source bundle does not state memory corruption, privilege escalation, denial of service, or confidentiality impact, so impact assessment requires vendor advisories or kernel maintainer context.

Mitigation direction

  • Update affected Linux kernels to vendor releases containing the stable kernel fixes.
  • Check Debian LTS and appliance vendor advisories for packaged kernel availability.
  • Prioritize vendor-supported kernel updates over source-level assumptions.
  • If updates are unavailable, follow vendor guidance for BPF-related risk reduction.

Validation and detection

  • Inventory systems running 32-bit Linux kernels in affected version ranges.
  • Confirm installed kernel builds include the referenced stable commits or vendor backports.
  • Review Debian LTS and Siemens advisories if those ecosystems are present.
  • Document any 32-bit systems where BPF functionality is available to untrusted workloads.
Prepared
Confidence
medium
Sources
12

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-26883 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
13Source 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

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

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux063c722dd9d285d877e6fd499e753d6224f4c046, 7e3a6b820535eb395784060ae26c5af579528fa0, 8032bf2af9ce26b3a362b9711d15f626ab946a74, 6183f4d3a0a2ad230511987c6c362ca43ec0055f, 6183f4d3a0a2ad230511987c6c362ca43ec0055f, 6183f4d3a0a2ad230511987c6c362ca43ec0055f, 6183f4d3a0a2ad230511987c6c362ca43ec0055f, 6183f4d3a0a2ad230511987c6c362ca43ec0055f, 6183f4d3a0a2ad230511987c6c362ca43ec0055f, 253150830a012adfccf90afcebae8fda5b05a80f, 766107351731ae223ebf60ca22bdfeb47ce6acc8, 4.19.177, 5.4.99, 5.10.17, 4.9.258, 4.14.222unaffected
LinuxLinux5.11, 0, 4.19.311, 5.4.273, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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