LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35905: bpf: Protect against int overflow for stack access size

In the Linux kernel, the following vulnerability has been resolved: bpf: Protect against int overflow for stack access size This patch re-introduces protection against the size of access to stack memory being negative; the access size can appear negative as a result of overflowing its signed int representation. This should not actually happen, as there are other protections along the way, but we should protect against it anyway. One code path was missing such protections (fixed in the previous patch in the series), causing out-of-bounds array accesses in check_stack_range_initialized(). This patch causes the verification of a program with such a non-sensical access size to fail. This check used to exist in a more indirect way, but was inadvertendly removed in a833a17aeac7.

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-35905 is a Linux kernel BPF verifier flaw. A nonsensical stack access size could overflow a signed integer and reach an out-of-bounds array access path. The source bundle does not provide CVSS, impact, or active exploitation evidence, so urgency depends on whether affected systems allow BPF programs to be loaded.

Executive priority

Treat this as a kernel hygiene priority for Linux fleets, not an emergency based on current evidence. Patch through normal accelerated kernel maintenance, with higher priority for shared compute and systems allowing BPF use.

Technical view

The Linux kernel BPF verifier missed protection for negative stack access sizes caused by signed int overflow. The vulnerable path involved check_stack_range_initialized(), and the fix makes verification fail for such invalid access sizes. The issue was introduced by removal of an earlier indirect check in a833a17aeac7.

Likely exposure

Linux systems running affected kernel versions are relevant, especially hosts where local users, containers, or services can load BPF programs. The bundle lists Linux as the affected product and references stable kernel fixes, but it does not define remote exposure or specific distributions beyond included advisories.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The vulnerability appears to require reaching BPF program verification, so exposure assessment should focus on local BPF loading permissions and kernel version state.

Researcher notes

Evidence supports a BPF verifier bounds-check flaw fixed upstream. The bundle lacks CVSS, exploitability analysis, and concrete impact statements. Avoid assuming privilege escalation or denial of service without additional vendor analysis.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Review Debian, Siemens, or platform-specific advisories where applicable.
  • Restrict untrusted ability to load BPF programs where operationally feasible.
  • Prioritize multi-user, container, and shared Linux hosts for review.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Map kernel builds to vendor advisories or the referenced stable commits.
  • Check whether untrusted users or workloads can load BPF programs.
  • Confirm updated systems booted into the remediated kernel.
Prepared
Confidence
medium
Sources
10

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-35905 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
9Source 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
LinuxLinuxafea95d319ccb4ad2060dece9ac5e2e364dec543, 02962684258eb53f414a8a59854767be526e6abb, b1d4d54d32ce6342f5faffe71bae736540ce7cb5, 08b91babccbb168353f8d43fea0ed28a4cad568c, a833a17aeac73b33f79433d7cee68d5cafd71e4f, a833a17aeac73b33f79433d7cee68d5cafd71e4f, 1858b8a331937f3976d8482cd5f6e1f945294ad3unaffected
LinuxLinux6.8, 0, 5.10.215, 5.15.154, 6.1.85, 6.6.26, 6.8.5, 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.