<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T03:51:55.194252+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2024-49954</id>
    <title>CVE-2024-49954 — static_call: Replace pointless WARN_ON() in static_call_module_notify()</title>
    <updated>2026-09-29T03:51:55.196471+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>static_call: Replace pointless WARN_ON() in static_call_module_notify()</p>
<p>static_call_module_notify() triggers a WARN_ON(), when memory allocation
fails in __static_call_add_module().</p>
<p>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.</p>
<p>A memory allocation fail is not a fatal problem, but the WARN_ON() takes
the machine out when panic_on_warn is set.</p>
<p>Replace it with a pr_warn().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-49954"/>
  </entry>
</feed>
