<?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>Wed, 30 Sep 2026 01:29:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80532 — xfs: fix another iunlink infinite loop bug in online fsck</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80532</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;xfs: fix another iunlink infinite loop bug in online fsck&lt;/p&gt;
&lt;p&gt;xrep_iunlink_resolve_bucket is supposed to reconstruct as much of the
incore prev and next unlinked list pointers based on what it finds on
disk and in memory before we move on to relinking the truly lost inodes
back into the unlinked list.  However, it&amp;#39;s still vulnerable to infinite
loops that come in via the next_unlinked pointers.&lt;/p&gt;
&lt;p&gt;Fix this problem by remembering which inodes we&amp;#39;ve already seen and
checking new agino pointers against that.  If a bit is already set,
either this is a loop or the inode has nonzero link count.  We&amp;#39;ll deal
with the second case in a subsequent patch.&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;xfs: fix another iunlink infinite loop bug in online fsck&lt;/p&gt;
&lt;p&gt;xrep_iunlink_resolve_bucket is supposed to reconstruct as much of the
incore prev and next unlinked list pointers based on what it finds on
disk and in memory before we move on to relinking the truly lost inodes
back into the unlinked list.  However, it&amp;#39;s still vulnerable to infinite
loops that come in via the next_unlinked pointers.&lt;/p&gt;
&lt;p&gt;Fix this problem by remembering which inodes we&amp;#39;ve already seen and
checking new agino pointers against that.  If a bit is already set,
either this is a loop or the inode has nonzero link count.  We&amp;#39;ll deal
with the second case in a subsequent patch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80532</guid>
    </item>
  </channel>
</rss>
