<?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>Thu, 01 Oct 2026 07:46:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54140 — nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54140</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 WARNING in mark_buffer_dirty due to discarded buffer reuse&lt;/p&gt;
&lt;p&gt;A syzbot stress test using a corrupted disk image reported that
mark_buffer_dirty() called from __nilfs_mark_inode_dirty() or
nilfs_palloc_commit_alloc_entry() may output a kernel warning, and can
panic if the kernel is booted with panic_on_warn.&lt;/p&gt;
&lt;p&gt;This is because nilfs2 keeps buffer pointers in local structures for some
metadata and reuses them, but such buffers may be forcibly discarded by
nilfs_clear_dirty_page() in some critical situations.&lt;/p&gt;
&lt;p&gt;This issue is reported to appear after commit 28a65b49eb53 (&amp;#34;nilfs2: do
not write dirty data after degenerating to read-only&amp;#34;), but the issue has
potentially existed before.&lt;/p&gt;
&lt;p&gt;Fix this issue by checking the uptodate flag when attempting to reuse an
internally held buffer, and reloading the metadata instead of reusing the
buffer if the flag was lost.&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 WARNING in mark_buffer_dirty due to discarded buffer reuse&lt;/p&gt;
&lt;p&gt;A syzbot stress test using a corrupted disk image reported that
mark_buffer_dirty() called from __nilfs_mark_inode_dirty() or
nilfs_palloc_commit_alloc_entry() may output a kernel warning, and can
panic if the kernel is booted with panic_on_warn.&lt;/p&gt;
&lt;p&gt;This is because nilfs2 keeps buffer pointers in local structures for some
metadata and reuses them, but such buffers may be forcibly discarded by
nilfs_clear_dirty_page() in some critical situations.&lt;/p&gt;
&lt;p&gt;This issue is reported to appear after commit 28a65b49eb53 (&amp;#34;nilfs2: do
not write dirty data after degenerating to read-only&amp;#34;), but the issue has
potentially existed before.&lt;/p&gt;
&lt;p&gt;Fix this issue by checking the uptodate flag when attempting to reuse an
internally held buffer, and reloading the metadata instead of reusing the
buffer if the flag was lost.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54140</guid>
    </item>
  </channel>
</rss>
