Description
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().
Metrics
CVSS 3.1 5.5/10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HAffected software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 9183c3f9ed710a8edf1a61e8a96d497258d26e08, < bc9356513d56b688775497b7ac6f2b967f46a80c; >= 9183c3f9ed710a8edf1a61e8a96d497258d26e08, < ea2cdf4da093d0482f0ef36ba971e2e0c7673425; >= 9183c3f9ed710a8edf1a61e8a96d497258d26e08, < e67534bd31d79952b50e791e92adf0b3e6c13b8c; >= 9183c3f9ed710a8edf1a61e8a96d497258d26e08, < 85a104aaef1f56623acc10ba4c42d5f046ba65b7; >= 9183c3f9ed710a8edf1a61e8a96d497258d26e08, < b83bef74c121a3311240fc4002d23486b85355e4; >= 9183c3f9ed710a8edf1a61e8a96d497258d26e08, < fe513c2ef0a172a58f158e2e70465c4317f0a9a2 |
| Linux | Linux | 5.10 |
References
- https://git.kernel.org/stable/c/85a104aaef1f56623acc10ba4c42d5f046ba65b7Patch
- https://git.kernel.org/stable/c/b83bef74c121a3311240fc4002d23486b85355e4Patch
- https://git.kernel.org/stable/c/bc9356513d56b688775497b7ac6f2b967f46a80cPatch
- https://git.kernel.org/stable/c/e67534bd31d79952b50e791e92adf0b3e6c13b8cPatch
- https://git.kernel.org/stable/c/ea2cdf4da093d0482f0ef36ba971e2e0c7673425Patch
- https://git.kernel.org/stable/c/fe513c2ef0a172a58f158e2e70465c4317f0a9a2Patch
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Timeline
- Published
- Oct 21, 2024
- Last modified
- Jun 17, 2026
- NVD status
- Modified