<?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 06:31:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-49987 — bpftool: Fix undefined behavior in qsort(NULL, 0, ...)</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-49987</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;bpftool: Fix undefined behavior in qsort(NULL, 0, ...)&lt;/p&gt;
&lt;p&gt;When netfilter has no entry to display, qsort is called with
qsort(NULL, 0, ...). This results in undefined behavior, as UBSan
reports:&lt;/p&gt;
&lt;p&gt;net.c:827:2: runtime error: null pointer passed as argument 1, which is declared to never be null&lt;/p&gt;
&lt;p&gt;Although the C standard does not explicitly state whether calling qsort
with a NULL pointer when the size is 0 constitutes undefined behavior,
Section 7.1.4 of the C standard (Use of library functions) mentions:&lt;/p&gt;
&lt;p&gt;&amp;#34;Each of the following statements applies unless explicitly stated
otherwise in the detailed descriptions that follow: If an argument to a
function has an invalid value (such as a value outside the domain of
the function, or a pointer outside the address space of the program, or
a null pointer, or a pointer to non-modifiable storage when the
corresponding parameter is not const-qualified) or a type (after
promotion) not expected by a function with variable number of
arguments, the behavior is undefined.&amp;#34;&lt;/p&gt;
&lt;p&gt;To avoid this, add an early return when nf_link_info is NULL to prevent
calling qsort with a NULL pointer.&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;bpftool: Fix undefined behavior in qsort(NULL, 0, ...)&lt;/p&gt;
&lt;p&gt;When netfilter has no entry to display, qsort is called with
qsort(NULL, 0, ...). This results in undefined behavior, as UBSan
reports:&lt;/p&gt;
&lt;p&gt;net.c:827:2: runtime error: null pointer passed as argument 1, which is declared to never be null&lt;/p&gt;
&lt;p&gt;Although the C standard does not explicitly state whether calling qsort
with a NULL pointer when the size is 0 constitutes undefined behavior,
Section 7.1.4 of the C standard (Use of library functions) mentions:&lt;/p&gt;
&lt;p&gt;&amp;#34;Each of the following statements applies unless explicitly stated
otherwise in the detailed descriptions that follow: If an argument to a
function has an invalid value (such as a value outside the domain of
the function, or a pointer outside the address space of the program, or
a null pointer, or a pointer to non-modifiable storage when the
corresponding parameter is not const-qualified) or a type (after
promotion) not expected by a function with variable number of
arguments, the behavior is undefined.&amp;#34;&lt;/p&gt;
&lt;p&gt;To avoid this, add an early return when nf_link_info is NULL to prevent
calling qsort with a NULL pointer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-49987</guid>
    </item>
  </channel>
</rss>
