CVE-2024-50262

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-11-09. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

November 9, 2024

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

bpf: Fix out-of-bounds write in trie_get_next_key() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13400ac8fb80c57c2bfb12ebd35ee121ce9b4d21
generic

bpf: Fix out-of-bounds write in trie_get_next_key() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c4b4f9a9ab82238cb158fa4fe61a8c0ae21a4980
generic

bpf: Fix out-of-bounds write in trie_get_next_key() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90a6e0e1e151ef7a9282e78f54c3091de2dcc99c
generic

bpf: Fix out-of-bounds write in trie_get_next_key() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a035df0b98df424559fd383e8e1a268f422ea2ba
generic

bpf: Fix out-of-bounds write in trie_get_next_key() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86c8ebe02d8806dd8878d0063e8e185622ab6ea6
generic

bpf: Fix out-of-bounds write in trie_get_next_key() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/590976f921723d53ac199c01d5b7b73a94875e68
generic

bpf: Fix out-of-bounds write in trie_get_next_key() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91afbc0eb3c90258ae378ae3c6ead3d2371e926d
generic

bpf: Fix out-of-bounds write in trie_get_next_key() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e8494ac079814a53fbc2258d2743e720907488ed

Vendor Advisories for CVE-2024-50262(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.134.145~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.133.132) @ jammy2026-05-21ubuntu
ubuntulinux-tools-ibm (5.15.0.1070.66) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.208.228~18.04.1) @ bionic2026-05-21ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1075.71) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-lts-20.04 (5.4.0.1143.145) @ focal2026-05-21ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.133.143~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-kvm (5.4.0.1127.123) @ focal2026-05-21ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1075.74) @ jammy2026-05-21ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1075.81~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1058 (5.4.0-1058.62) @ focal2026-05-21ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1072.70) @ jammy2026-05-21ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1073.73) @ jammy2026-05-21ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1078.80) @ jammy2026-05-21ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1138.131) @ focal2026-05-21ubuntu
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1086.115) @ focal2026-05-21ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-21ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-21ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-05-21ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-05-21ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-05-21ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-05-21ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-05-21ubuntu
redhatkernel-0:5.14.0-503.19.1.el9_52024-12-19redhat
redhatkernel-0:5.14.0-427.48.1.el9_42024-12-11redhat
linuxKernel @ 4.19.323osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Data Freshness Timeline

(refreshed 13× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 142 total refreshes for this CVE.

  1. 2026-08-07 16:25 UTCEPSS rescore
  2. 2026-08-06 13:45 UTCEPSS rescore
  3. 2026-08-05 19:16 UTCEPSS rescore
  4. 2026-08-05 11:54 UTCEG score recompute
  5. 2026-08-05 11:54 UTCVendor advisory
  6. 2026-08-05 11:54 UTCGHSA enrichment
  7. 2026-08-04 15:08 UTCEPSS rescore
  8. 2026-08-04 11:24 UTCEG score recompute
  9. 2026-08-04 11:24 UTCVendor advisory
  10. 2026-08-04 11:24 UTCGHSA enrichment
  11. 2026-08-04 10:36 UTCEPSS rescore
  12. 2026-08-03 10:34 UTCEPSS rescore
  13. 2026-08-02 02:25 UTCEPSS rescore
  14. 2026-08-01 04:14 UTCEPSS rescore
  15. 2026-08-01 04:14 UTCEPSS rescore
  16. 2026-07-30 16:26 UTCEPSS rescore
  17. 2026-07-30 01:29 UTCEPSS rescore
  18. 2026-07-28 15:35 UTCEPSS rescore
  19. 2026-07-28 08:25 UTCOSV refresh
  20. 2026-07-27 14:11 UTCEPSS rescore
  21. 2026-07-26 14:53 UTCEPSS rescore
  22. 2026-07-26 14:53 UTCEPSS rescore
  23. 2026-07-25 14:17 UTCEPSS rescore
  24. 2026-07-25 14:16 UTCEPSS rescore
  25. 2026-07-24 14:16 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 14:17 UTCEPSS rescore
  2. 2026-07-23 14:17 UTCEPSS rescore
  3. 2026-07-23 02:42 UTCEG score recompute
  4. 2026-07-22 14:07 UTCEPSS rescore
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-20 17:06 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 14:30 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-19 02:28 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-16 17:02 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 01:59 UTCEPSS rescore
  17. 2026-07-15 01:59 UTCEPSS rescore
  18. 2026-07-13 22:29 UTCEPSS rescore
  19. 2026-07-13 06:12 UTCEPSS rescore
  20. 2026-07-12 05:45 UTCEPSS rescore
  21. 2026-07-12 05:45 UTCEPSS rescore
  22. 2026-07-11 08:26 UTCEPSS rescore
  23. 2026-07-11 00:22 UTCOSV refresh
  24. 2026-07-09 19:09 UTCEPSS rescore
  25. 2026-07-09 19:09 UTCEPSS rescore
  26. 2026-07-08 15:14 UTCEPSS rescore
  27. 2026-07-07 13:45 UTCEPSS rescore
  28. 2026-07-06 16:26 UTCEPSS rescore
  29. 2026-07-06 02:22 UTCEPSS rescore
  30. 2026-07-05 02:29 UTCEPSS rescore
  31. 2026-07-04 06:30 UTCEPSS rescore
  32. 2026-07-01 15:05 UTCEPSS rescore
  33. 2026-06-30 23:21 UTCEPSS rescore
  34. 2026-06-29 14:05 UTCEPSS rescore
  35. 2026-06-28 14:07 UTCEPSS rescore
  36. 2026-06-28 04:55 UTCEPSS rescore
  37. 2026-06-28 04:55 UTCEPSS rescore
  38. 2026-06-27 03:07 UTCEPSS rescore
  39. 2026-06-27 03:07 UTCEPSS rescore
  40. 2026-06-25 13:49 UTCEPSS rescore
  41. 2026-06-24 14:04 UTCEPSS rescore
  42. 2026-06-24 14:04 UTCEPSS rescore
  43. 2026-06-23 21:32 UTCEPSS rescore
  44. 2026-06-23 21:32 UTCEPSS rescore
  45. 2026-06-22 14:25 UTCEPSS rescore
  46. 2026-06-22 14:25 UTCEPSS rescore
  47. 2026-06-22 07:31 UTCOSV refresh
  48. 2026-06-21 14:56 UTCEPSS rescore
  49. 2026-06-21 01:59 UTCEPSS rescore
  50. 2026-06-21 01:58 UTCEPSS rescore
  51. 2026-06-19 19:25 UTCEPSS rescore
  52. 2026-06-18 17:52 UTCEPSS rescore
  53. 2026-06-18 17:52 UTCEPSS rescore
  54. 2026-06-17 17:52 UTCEPSS rescore
  55. 2026-06-17 17:52 UTCEPSS rescore
  56. 2026-06-16 17:52 UTCEPSS rescore
  57. 2026-06-16 17:52 UTCEPSS rescore
  58. 2026-06-15 17:47 UTCEPSS rescore
  59. 2026-06-14 23:17 UTCEPSS rescore
  60. 2026-06-13 22:59 UTCEPSS rescore
  61. 2026-06-13 22:59 UTCEPSS rescore
  62. 2026-06-13 22:59 UTCEPSS rescore
  63. 2026-06-12 23:11 UTCEPSS rescore
  64. 2026-06-12 23:11 UTCEPSS rescore
  65. 2026-06-11 13:59 UTCEPSS rescore
  66. 2026-06-10 22:18 UTCEPSS rescore
  67. 2026-06-10 13:21 UTCEPSS rescore
  68. 2026-06-08 14:16 UTCEPSS rescore
  69. 2026-06-08 14:16 UTCEPSS rescore
  70. 2026-06-07 15:24 UTCEPSS rescore
  71. 2026-06-07 15:24 UTCEPSS rescore
  72. 2026-06-06 13:46 UTCEPSS rescore
  73. 2026-06-06 13:46 UTCEPSS rescore
  74. 2026-06-05 22:46 UTCEPSS rescore
  75. 2026-06-05 22:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-50262?
CVE-2024-50262 is a high vulnerability published on November 9, 2024. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix out-of-bounds write in triegetnext_key() triegetnextkey() allocates a node stack with size trie->maxprefixlen, while it writes (trie->max_prefixlen + 1) nodes to the stack when it has full paths from the root to leaves.…
When was CVE-2024-50262 disclosed?
CVE-2024-50262 was first published in the National Vulnerability Database on November 9, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-50262 actively exploited?
CVE-2024-50262 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.4% of all scored CVEs.
What is the CVSS score of CVE-2024-50262?
CVE-2024-50262 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-50262?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-50262, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-50262

Explore →

Is Your Infrastructure Affected by CVE-2024-50262?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.