---
id: CVE-2024-50262
title: |-
  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)…
summary: |-
  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)…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-787
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 4.16, < 4.19.323'
  - 'linux_kernel >= 4.20, < 5.4.285'
  - 'linux_kernel >= 5.5, < 5.10.229'
  - 'linux_kernel >= 5.11, < 5.15.171'
  - 'linux_kernel >= 5.16, < 6.1.116'
  - 'linux_kernel >= 6.2, < 6.6.60'
  - 'linux_kernel >= 6.7, < 6.11.7'
  - linux_kernel = 6.12
patched:
  - linux_kernel 6.11.7
published: '2024-11-09'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T01:19:11.013'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-50262'
references:
  - url: 'https://git.kernel.org/stable/c/13400ac8fb80c57c2bfb12ebd35ee121ce9b4d21'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/590976f921723d53ac199c01d5b7b73a94875e68'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/86c8ebe02d8806dd8878d0063e8e185622ab6ea6'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/90a6e0e1e151ef7a9282e78f54c3091de2dcc99c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/91afbc0eb3c90258ae378ae3c6ead3d2371e926d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a035df0b98df424559fd383e8e1a268f422ea2ba'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c4b4f9a9ab82238cb158fa4fe61a8c0ae21a4980'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e8494ac079814a53fbc2258d2743e720907488ed'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-265688.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-355557.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-398330.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.0027
epssPercentile: 0.19028
ingestedAt: '2026-10-15T03:30:12.767Z'
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2024-12-11T15:09:18.664200Z'
---

## Overview

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.

## Affected

- `linux_kernel >= 4.16, < 4.19.323`
- `linux_kernel >= 4.20, < 5.4.285`
- `linux_kernel >= 5.5, < 5.10.229`
- `linux_kernel >= 5.11, < 5.15.171`
- `linux_kernel >= 5.16, < 6.1.116`
- `linux_kernel >= 6.2, < 6.6.60`
- `linux_kernel >= 6.7, < 6.11.7`
- `linux_kernel = 6.12`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.11.7`