<?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 23:50:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80804 — xfs: restore nofs context unconditionally in xfs_trans_roll</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80804</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: restore nofs context unconditionally in xfs_trans_roll&lt;/p&gt;
&lt;p&gt;When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context
is cleared but only restored in the success path.  This leaves the
error path without nofs protection, causing a circular lock dependency
between xfs_nondir_ilock_class and fs_reclaim:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(&amp;amp;xfs_nondir_ilock_class);
                               lock(fs_reclaim);
                               lock(&amp;amp;xfs_nondir_ilock_class);
  lock(fs_reclaim);&lt;/p&gt;
&lt;p&gt;Fix this by moving xfs_trans_set_context() before the error check so
that nofs context is always restored on the new transaction.&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: restore nofs context unconditionally in xfs_trans_roll&lt;/p&gt;
&lt;p&gt;When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context
is cleared but only restored in the success path.  This leaves the
error path without nofs protection, causing a circular lock dependency
between xfs_nondir_ilock_class and fs_reclaim:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(&amp;amp;xfs_nondir_ilock_class);
                               lock(fs_reclaim);
                               lock(&amp;amp;xfs_nondir_ilock_class);
  lock(fs_reclaim);&lt;/p&gt;
&lt;p&gt;Fix this by moving xfs_trans_set_context() before the error check so
that nofs context is always restored on the new transaction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80804</guid>
    </item>
  </channel>
</rss>
