CVE-2024-50262: bpf: Fix out-of-bounds write in trie_get_next_key()
bpf: Fix out-of-bounds write in triegetnextkey()
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.64.2-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 5.15.173.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50262?
CVE-2024-50262 has not been assigned a specific severity rating, but it impacts the Linux kernel's memory management.
How do I fix CVE-2024-50262?
To fix CVE-2024-50262, update your Linux kernel to a version that includes the patch for this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-50262?
CVE-2024-50262 affects Linux kernel versions between 4.16 and 6.12-rc5.
What is the nature of the vulnerability in CVE-2024-50262?
CVE-2024-50262 involves an out-of-bounds write in the trie_get_next_key() function in the Linux kernel.
Does CVE-2024-50262 require any special action to exploit?
Exploitation of CVE-2024-50262 requires specific conditions, typically involving crafted input that triggers the out-of-bounds write.