CVE-2024-50162: bpf: devmap: provide rxq after redirect
bpf: devmap: provide rxq after redirect
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.223-1Fixed 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-50162?
CVE-2024-50162 has a medium severity rating due to its potential impact on BPF programs post-redirect.
How do I fix CVE-2024-50162?
To fix CVE-2024-50162, update your Linux kernel to a version that is not affected, specifically versions beyond the specified vulnerable ranges.
Which versions of the Linux kernel are affected by CVE-2024-50162?
CVE-2024-50162 affects Linux kernel versions from 5.14 to 5.15.170, 5.16 to 6.1.115, 6.2 to 6.6.59, and 6.7 to 6.11.6, including specific release candidates.
What are the implications of CVE-2024-50162 for BPF programs?
The implications of CVE-2024-50162 for BPF programs include possible incorrect behavior or exploitation due to the absence of a necessary device pointer after redirecting.
Is there a public database of vulnerabilities like CVE-2024-50162?
Yes, vulnerabilities like CVE-2024-50162 are tracked and documented in public databases like the National Vulnerability Database (NVD) and MITRE's CVE database.