CVE-2024-50167: be2net: fix potential memory leak in be_xmit()
be2net: fix potential memory leak in bexmit()
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 5.15.173.1-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.64.2-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50167?
CVE-2024-50167 has a moderate severity level due to a potential memory leak in the be_xmit function.
How do I fix CVE-2024-50167?
To fix CVE-2024-50167, upgrade to a patched version of the Linux kernel that addresses the memory leak issue.
Which Linux kernel versions are affected by CVE-2024-50167?
CVE-2024-50167 affects Linux kernel versions ranging from 4.2 to 6.12-rc4.
Is there a workaround for CVE-2024-50167?
Currently, there are no known effective workarounds for CVE-2024-50167 other than updating to a secure version of the kernel.
What component of the Linux kernel is impacted by CVE-2024-50167?
CVE-2024-50167 impacts the be2net component within the Linux kernel.