Bug 2324892 (CVE-2024-50262) - CVE-2024-50262 kernel: bpf: Fix out-of-bounds write in trie_get_next_key()
Summary: CVE-2024-50262 kernel: bpf: Fix out-of-bounds write in trie_get_next_key()
Keywords:
Status: NEW
Alias: CVE-2024-50262
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2325115
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-09 11:03 UTC by OSIDB Bzimport
Modified: 2025-04-25 17:25 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2025:0001 0 None None None 2025-01-01 07:23:45 UTC
Red Hat Product Errata RHSA-2024:10942 0 None None None 2024-12-11 01:19:50 UTC
Red Hat Product Errata RHSA-2024:11486 0 None None None 2024-12-19 00:43:33 UTC

Description OSIDB Bzimport 2024-11-09 11:03:38 UTC
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.

Comment 1 Avinash Hanwate 2024-11-11 06:34:36 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024110955-CVE-2024-50262-9cd7@gregkh/T

Comment 2 errata-xmlrpc 2024-12-11 01:19:49 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Extended Update Support

Via RHSA-2024:10942 https://access.redhat.com/errata/RHSA-2024:10942

Comment 3 errata-xmlrpc 2024-12-19 00:43:31 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:11486 https://access.redhat.com/errata/RHSA-2024:11486


Note You need to log in before you can comment on or make changes to this bug.