static_call: Replace pointless WARN_ON() in static_call_module_notify()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9183c3f9ed710a8edf1a61e8a96d497258d26e08 · < fe513c2ef0a172a58f158e2e70465c4317f0a9a2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
static_call: Replace pointless WARN_ON() in static_call_module_notify()
static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module().
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 WARN_ON() takes the machine out when panic_on_warn is set.
Replace it with a pr_warn().
From the CVE record · Linux
A memory allocation failure in static_call_module_notify() triggers a WARN_ON() even though the error is handled and passed to the initiating userspace application. If panic_on_warn is enabled, the warning can take the machine down; the input does not establish how an attacker could trigger the failure or whether authentication or user interaction is required.
Operators running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified.