CVE-2024-49954: Linux kernel · static_call: Replace pointless WARN_ON() in static_call_module_notify()
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1073.79~20.04.1 : update Linux kernel when convenient.
Data as of 29 Oct 2026, 22:34 UTC
- Patch
- Available – fixed in 5.15.0-1073.79~20.04.1, 5.15.0-1078.87~20.04.1, 5.15.0-1072.80~20.04.1 +58
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7166-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7194-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7304-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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().
References
- ubuntu.com/security/CVE-2024-49954 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-49954 (opens in a new tab)
- git.kernel.org/linus/fe513c2ef0a172a58f158e2e70465c4317f0a9a2 (opens in a new tab)
- git.kernel.org/stable/c/bc9356513d56b688775497b7ac6f2b967f46a80c (opens in a new tab)
- git.kernel.org/stable/c/ea2cdf4da093d0482f0ef36ba971e2e0c7673425 (opens in a new tab)
- git.kernel.org/stable/c/e67534bd31d79952b50e791e92adf0b3e6c13b8c (opens in a new tab)
- git.kernel.org/stable/c/85a104aaef1f56623acc10ba4c42d5f046ba65b7 (opens in a new tab)
- git.kernel.org/stable/c/b83bef74c121a3311240fc4002d23486b85355e4 (opens in a new tab)
- git.kernel.org/stable/c/fe513c2ef0a172a58f158e2e70465c4317f0a9a2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7194-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-1 (opens in a new tab)