CVE-2024-50064: zram: free secondary algorithms names
In the Linux kernel, the following vulnerability has been resolved:
zram: free secondary algorithms names
We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory.
[senozhatsky: kfree(NULL) is legal] Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org
Other sources
In the Linux kernel, the following vulnerability has been resolved:
zram: free secondary algorithms names
We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory.
[senozhatsky@chromium.org: kfree(NULL) is legal]
— NVD
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
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50064?
CVE-2024-50064 has a medium severity level due to a memory leak vulnerability in the Linux kernel.
How do I fix CVE-2024-50064?
To fix CVE-2024-50064, update your Linux kernel to a patched version that addresses this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-50064?
CVE-2024-50064 affects Linux kernel versions between 6.2 and 6.6.57, and between 6.7 and 6.11.4.
What component of the Linux kernel does CVE-2024-50064 affect?
CVE-2024-50064 affects the zram component of the Linux kernel.
Is there a risk of exploiting CVE-2024-50064 in production environments?
Yes, CVE-2024-50064 could lead to memory leaks that may impact system stability in production environments.