CVE-2024-26884: bpf: Fix hashtab overflow check on 32-bit arches
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix hashtab overflow check on 32-bit arches
The hashtab 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. So apply the same
fix to hashtab, by moving the overflow check to before the roundup.
Security readout for executives and security teams
Plain-English summary
A Linux kernel BPF hash-table calculation can overflow on 32-bit systems before its safety check runs. A local, low-privileged attacker who can reach the affected BPF path could potentially compromise confidentiality, integrity, or availability. The supplied sources document corrected kernel code but do not establish real-world exploitation.
Executive priority
Treat this as a high-priority patching issue for exposed 32-bit Linux systems, but not as an internet-wide emergency. Prioritize multi-user hosts, embedded devices, appliances, and workload platforms where untrusted local code may execute. Normal expedited maintenance is appropriate unless internal exposure analysis shows the vulnerable path is broadly reachable.
Technical view
The BPF hashtab implementation used roundup_pow_of_two() before checking for a zero result. On 32-bit architectures, an unsigned-long left shift could overflow with undefined behavior, undermining that check. Syzbot triggered the analogous condition in DEVMAP_HASH. Stable fixes move overflow validation before rounding. The issue is classified as CWE-190 with CVSS 3.1 score 7.8.
Likely exposure
Exposure is concentrated on 32-bit Linux kernels containing the vulnerable BPF hashtab logic, particularly where local users or workloads can access relevant BPF functionality. The supplied normalized version list does not provide sufficiently clear range semantics for reliable downstream identification. Kernel distributors and appliance vendors may backport fixes, so package versions must be checked against their advisories.
Exploitation context
The CVSS vector describes a local attack requiring low privileges, low complexity, and no user interaction. Syzbot triggered the defect during automated testing. The CVE is not identified as KEV, and the supplied sources provide no evidence of active exploitation or a public weaponized exploit.
Researcher notes
The defect concerns the placement of an integer-overflow check, not merely a missing check. Undefined behavior occurs during power-of-two rounding before the original zero-result validation. The source description connects the hashtab correction to an analogous DEVMAP_HASH failure. Exact exploitability, reachable map types, and downstream kernel boundaries are not fully established by the bundle.
Mitigation direction
Apply a vendor-supplied kernel update containing the relevant Linux stable fix for your maintained branch.
Prioritize affected 32-bit systems where local users or workloads can access BPF functionality.
Reboot into the updated kernel and retire vulnerable kernel packages according to change-control policy.
Check vendor guidance when the bundled version data does not map cleanly to downstream kernels.
Validation and detection
Inventory running kernel versions and CPU architecture, separating 32-bit systems from 64-bit systems.
Map each kernel to its distributor advisory or the applicable upstream stable fix commit.
Confirm the running kernel, not merely an installed package, contains the fix.
Review local BPF access and untrusted-user exposure while remediation is pending.
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.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
3ADP providers
13Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.