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

> An out-of-bounds write in the Linux kernel BPF trie implementation allows attackers to corrupt memory, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Nov 2024
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-53042, AZL-53099, BELL-CVE-2024-50262, DEBIAN-CVE-2024-50262, GHSA-m4m9-v4mx-256j, UBUNTU-CVE-2024-50262

## What is CVE-2024-50262?

CVE-2024-50262 is a high-severity memory corruption vulnerability in Linux kernel, published on 9 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2024-50262?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-50262?

Apply the vendor's patch.

## Is CVE-2024-50262 being exploited?

There is no known exploitation of CVE-2024-50262 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50262 and fix it if it is affected.

What it is: CVE-2024-50262 is a high-severity memory corruption vulnerability in Linux kernel, published on 9 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50262 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-50262/ (Markdown: https://insights.sbomify.com/CVE-2024-50262/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50262
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50262
- OSV: https://osv.dev/vulnerability/CVE-2024-50262

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50262/
Summaries are generated and may contain mistakes; the official description above is the record.