LiveActive security incident?Get immediate response
CVE Record

CVE-2024-50262: bpf: Fix out-of-bounds write in trie_get_next_key()

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix out-of-bounds write in trie_get_next_key() trie_get_next_key() allocates a node stack with size trie->max_prefixlen, while it writes (trie->max_prefixlen + 1) nodes to the stack when it has full paths from the root to leaves. For example, consider a trie with max_prefixlen is 8, and the nodes with key 0x00/0, 0x00/1, 0x00/2, ... 0x00/8 inserted. Subsequent calls to trie_get_next_key with _key with .prefixlen = 8 make 9 nodes be written on the node stack with size 8.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-50262 is a Linux kernel BPF bug where a local user with required privileges could trigger memory corruption in trie key iteration. The impact is high because kernel memory corruption can affect confidentiality, integrity, and availability. The source bundle does not show confirmed active exploitation.

Executive priority

Prioritize remediation in the normal high-severity kernel patch cycle, accelerated for shared infrastructure or systems with untrusted local access. There is no supplied evidence of active exploitation, but the impact profile justifies timely patching and vendor-advisory tracking.

Technical view

The bug is an out-of-bounds write in trie_get_next_key(). The function allocates a node stack sized to trie->max_prefixlen but can write trie->max_prefixlen + 1 entries when traversing full root-to-leaf paths. It is classified as CWE-787 with CVSS 3.1 score 7.8 and local, low-complexity, privileged attack conditions.

Likely exposure

Exposure is most relevant on Linux systems where affected kernels are deployed and local users or workloads can reach BPF map functionality. The bundle lists Linux kernel versions beginning at 4.16 and stable fix points including 4.19.323, 5.4.285, 5.10.229, 5.15.171, 6.1.116, 6.6.60, 6.11.7, and 6.12.

Exploitation context

The provided sources support local exploitation potential with low complexity and privileges required. They do not identify remote exploitation, public exploit availability, or CISA KEV listing. Treat this as a local privilege and kernel stability risk, especially on shared Linux hosts, container platforms, and appliances using affected kernels.

Researcher notes

Focus validation on kernel lineage and BPF LPM trie exposure rather than remote scanning. The root issue is stack sizing versus traversal depth in trie_get_next_key(). Evidence is sufficient for impact and remediation direction, but incomplete for exploit availability, distro-specific fixed package versions, and all downstream products.

Mitigation direction

  • Upgrade to vendor-provided kernels containing the referenced stable fixes.
  • Check Linux distribution advisories for package names and exact fixed builds.
  • Prioritize shared hosts, container nodes, and systems with untrusted local users.
  • Review vendor advisories for embedded or appliance products using Linux kernels.
  • If patching is delayed, follow vendor guidance on reducing BPF exposure.

Validation and detection

  • Inventory running kernel versions across Linux servers, appliances, and containers hosts.
  • Compare installed kernels with distribution advisories and referenced fixed stable versions.
  • Confirm BPF-related exposure assumptions for local users and workload isolation boundaries.
  • Verify Debian LTS or vendor kernel packages are updated where applicable.
  • Track Siemens advisories for affected industrial products, if in scope.
Prepared
Confidence
high
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.

cwe · low confidence lookup

CWE-787: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-50262 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
3ADP providers
14Source links

SSVC decision data

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

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-50262Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
cvssV3_1other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb471f2f1de8b816f1e799b80aa92588f3566e4bd, b471f2f1de8b816f1e799b80aa92588f3566e4bd, b471f2f1de8b816f1e799b80aa92588f3566e4bd, b471f2f1de8b816f1e799b80aa92588f3566e4bd, b471f2f1de8b816f1e799b80aa92588f3566e4bd, b471f2f1de8b816f1e799b80aa92588f3566e4bd, b471f2f1de8b816f1e799b80aa92588f3566e4bd, b471f2f1de8b816f1e799b80aa92588f3566e4bdunaffected
LinuxLinux4.16, 0, 4.19.323, 5.4.285, 5.10.229, 5.15.171, 6.1.116, 6.6.60, 6.11.7, 6.12affected
Weakness

CWE details

CWE-787

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs