<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 03:51:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-49954 — static_call: Replace pointless WARN_ON() in static_call_module_notify()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-49954</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;static_call: Replace pointless WARN_ON() in static_call_module_notify()&lt;/p&gt;
&lt;p&gt;static_call_module_notify() triggers a WARN_ON(), when memory allocation
fails in __static_call_add_module().&lt;/p&gt;
&lt;p&gt;That&amp;#39;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.&lt;/p&gt;
&lt;p&gt;A memory allocation fail is not a fatal problem, but the WARN_ON() takes
the machine out when panic_on_warn is set.&lt;/p&gt;
&lt;p&gt;Replace it with a pr_warn().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;static_call: Replace pointless WARN_ON() in static_call_module_notify()&lt;/p&gt;
&lt;p&gt;static_call_module_notify() triggers a WARN_ON(), when memory allocation
fails in __static_call_add_module().&lt;/p&gt;
&lt;p&gt;That&amp;#39;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.&lt;/p&gt;
&lt;p&gt;A memory allocation fail is not a fatal problem, but the WARN_ON() takes
the machine out when panic_on_warn is set.&lt;/p&gt;
&lt;p&gt;Replace it with a pr_warn().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-49954</guid>
    </item>
  </channel>
</rss>
