Skip to main content
VulnerabilityPublished Updated

CVE-2024-49954: Linux kernel · static_call: Replace pointless WARN_ON() in static_call_module_notify()

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 29 Oct 2026, 23:59 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

AI-suggested

A fix is available that replaces the WARN_ON() call with a pr_warn() to prevent kernel panics on memory allocation failure. Users should apply the official Linux kernel update that includes this patch to mitigate the issue.

Description

CVE-2024-49954 addresses a Linux kernel issue where static_call_module_notify() triggers a WARN_ON() on memory allocation failure in __static_call_add_module(). This warning is unnecessary because the failure is already handled properly by the call chain and the error code is passed to userspace. The WARN_ON() can cause a kernel panic if panic_on_warn is enabled. The fix replaces WARN_ON() with a pr_warn() to avoid unnecessary panics.

References

Community reviews

Loading reviews…