<?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 01:27:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97552 — xfs: initialise error in xfs_defer_finish_one()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97552</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: initialise error in xfs_defer_finish_one()&lt;/p&gt;
&lt;p&gt;xfs_defer_finish_one() declares error without an initialiser and only
assigns it inside the loop over dfp-&amp;gt;dfp_work.  When that list is empty
the loop body never runs, control falls through to the &amp;#34;Done with the
dfp, free it&amp;#34; path, and the function returns an indeterminate value.&lt;/p&gt;
&lt;p&gt;An item-less pending item reaches this through xfs_defer_add_barrier(),
which xfs_reap_ag_blocks() uses on any CONFIG_XFS_ONLINE_REPAIR kernel.
xfs_defer_finish_noroll() treats any non-EAGAIN return as fatal, so a
non-zero stack value turns a successful barrier into a
SHUTDOWN_CORRUPT_INCORE in the middle of a repair.  Zero is the correct
result: reaching the free path means the item loop drained without a
non-zero error.&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: initialise error in xfs_defer_finish_one()&lt;/p&gt;
&lt;p&gt;xfs_defer_finish_one() declares error without an initialiser and only
assigns it inside the loop over dfp-&amp;gt;dfp_work.  When that list is empty
the loop body never runs, control falls through to the &amp;#34;Done with the
dfp, free it&amp;#34; path, and the function returns an indeterminate value.&lt;/p&gt;
&lt;p&gt;An item-less pending item reaches this through xfs_defer_add_barrier(),
which xfs_reap_ag_blocks() uses on any CONFIG_XFS_ONLINE_REPAIR kernel.
xfs_defer_finish_noroll() treats any non-EAGAIN return as fatal, so a
non-zero stack value turns a successful barrier into a
SHUTDOWN_CORRUPT_INCORE in the middle of a repair.  Zero is the correct
result: reaching the free path means the item loop drained without a
non-zero error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97552</guid>
    </item>
  </channel>
</rss>
