<?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://db.gcve.eu</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 21:15:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90420 — nilfs2: fix infinite loop in nilfs_clean_segments()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-90420</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;nilfs2: fix infinite loop in nilfs_clean_segments()&lt;/p&gt;
&lt;p&gt;syzbot reported a hung task in nilfs_transaction_begin(). This occurs
because the cleaner ioctl falls into an infinite loop if
nilfs_segctor_construct() repeatedly returns -EROFS (e.g. the device
is remounted as read-only after an I/O error).&lt;/p&gt;
&lt;p&gt;Currently in nilfs_clean_segments(), if err is non-zero, it logs the
error and sleeps but doesn&amp;#39;t abort when it encounters a terminal error
like -EROFS. This causes the thread to loop forever.&lt;/p&gt;
&lt;p&gt;Fix this by breaking out of the loop if nilfs_segctor_construct()
returns -EROFS. This matches the behaviour in
nilfs_segctor_write_out(), which also handles -EROFS.&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;nilfs2: fix infinite loop in nilfs_clean_segments()&lt;/p&gt;
&lt;p&gt;syzbot reported a hung task in nilfs_transaction_begin(). This occurs
because the cleaner ioctl falls into an infinite loop if
nilfs_segctor_construct() repeatedly returns -EROFS (e.g. the device
is remounted as read-only after an I/O error).&lt;/p&gt;
&lt;p&gt;Currently in nilfs_clean_segments(), if err is non-zero, it logs the
error and sleeps but doesn&amp;#39;t abort when it encounters a terminal error
like -EROFS. This causes the thread to loop forever.&lt;/p&gt;
&lt;p&gt;Fix this by breaking out of the loop if nilfs_segctor_construct()
returns -EROFS. This matches the behaviour in
nilfs_segctor_write_out(), which also handles -EROFS.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-90420</guid>
    </item>
  </channel>
</rss>
