<?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>Sun, 04 Oct 2026 11:03:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-47739 — padata: use integer wrap around to prevent deadlock on seq_nr overflow</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-47739</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;padata: use integer wrap around to prevent deadlock on seq_nr overflow&lt;/p&gt;
&lt;p&gt;When submitting more than 2^32 padata objects to padata_do_serial, the
current sorting implementation incorrectly sorts padata objects with
overflowed seq_nr, causing them to be placed before existing objects in
the reorder list. This leads to a deadlock in the serialization process
as padata_find_next cannot match padata-&amp;gt;seq_nr and pd-&amp;gt;processed
because the padata instance with overflowed seq_nr will be selected
next.&lt;/p&gt;
&lt;p&gt;To fix this, we use an unsigned integer wrap around to correctly sort
padata objects in scenarios with integer overflow.&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;padata: use integer wrap around to prevent deadlock on seq_nr overflow&lt;/p&gt;
&lt;p&gt;When submitting more than 2^32 padata objects to padata_do_serial, the
current sorting implementation incorrectly sorts padata objects with
overflowed seq_nr, causing them to be placed before existing objects in
the reorder list. This leads to a deadlock in the serialization process
as padata_find_next cannot match padata-&amp;gt;seq_nr and pd-&amp;gt;processed
because the padata instance with overflowed seq_nr will be selected
next.&lt;/p&gt;
&lt;p&gt;To fix this, we use an unsigned integer wrap around to correctly sort
padata objects in scenarios with integer overflow.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-47739</guid>
    </item>
  </channel>
</rss>
