CVE-2024-49954: static_call: Replace pointless WARN_ON() in static_call_module_notify()
In the Linux kernel, the following vulnerability has been resolved:
staticcall: Replace pointless WARNON() in staticcallmodulenotify()
staticcallmodulenotify() triggers a WARNON(), when memory allocation fails in staticcalladdmodule().
That's not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application.
A memory allocation fail is not a fatal problem, but the WARNON() takes the machine out when paniconwarn is set.
Replace it with a prwarn().
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
Event History
Frequently Asked Questions
What is the severity of CVE-2024-49954?
CVE-2024-49954 has a low severity rating as it involves a minor issue regarding a WARN_ON() trigger on memory allocation failure.
How do I fix CVE-2024-49954?
To fix CVE-2024-49954, you should upgrade your Linux kernel to a version that resolves this issue, such as 6.1.123-1 or later.
Which versions of the Linux kernel are affected by CVE-2024-49954?
CVE-2024-49954 affects Linux kernel versions between 5.10 and 5.15.168, and from 5.16 to 6.6.55.
Is there a workaround for CVE-2024-49954?
There is no known workaround for CVE-2024-49954, and the best approach is to apply the recommended updates.
Who is affected by CVE-2024-49954?
Users of the Linux kernel across the affected versions are vulnerable to CVE-2024-49954.