<?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://cve.radiocsirt.org</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>Fri, 09 Oct 2026 18:49:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-38582 — nilfs2: fix potential hang in nilfs_detach_log_writer()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-38582</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 potential hang in nilfs_detach_log_writer()&lt;/p&gt;
&lt;p&gt;Syzbot has reported a potential hang in nilfs_detach_log_writer() called
during nilfs2 unmount.&lt;/p&gt;
&lt;p&gt;Analysis revealed that this is because nilfs_segctor_sync(), which
synchronizes with the log writer thread, can be called after
nilfs_segctor_destroy() terminates that thread, as shown in the call trace
below:&lt;/p&gt;
&lt;p&gt;nilfs_detach_log_writer
  nilfs_segctor_destroy
    nilfs_segctor_kill_thread  --&amp;gt; Shut down log writer thread
    flush_work
      nilfs_iput_work_func
        nilfs_dispose_list
          iput
            nilfs_evict_inode
              nilfs_transaction_commit
                nilfs_construct_segment (if inode needs sync)
                  nilfs_segctor_sync  --&amp;gt; Attempt to synchronize with
                                          log writer thread
                           *** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;Fix this issue by changing nilfs_segctor_sync() so that the log writer
thread returns normally without synchronizing after it terminates, and by
forcing tasks that are already waiting to complete once after the thread
terminates.&lt;/p&gt;
&lt;p&gt;The skipped inode metadata flushout will then be processed together in the
subsequent cleanup work in nilfs_segctor_destroy().&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 potential hang in nilfs_detach_log_writer()&lt;/p&gt;
&lt;p&gt;Syzbot has reported a potential hang in nilfs_detach_log_writer() called
during nilfs2 unmount.&lt;/p&gt;
&lt;p&gt;Analysis revealed that this is because nilfs_segctor_sync(), which
synchronizes with the log writer thread, can be called after
nilfs_segctor_destroy() terminates that thread, as shown in the call trace
below:&lt;/p&gt;
&lt;p&gt;nilfs_detach_log_writer
  nilfs_segctor_destroy
    nilfs_segctor_kill_thread  --&amp;gt; Shut down log writer thread
    flush_work
      nilfs_iput_work_func
        nilfs_dispose_list
          iput
            nilfs_evict_inode
              nilfs_transaction_commit
                nilfs_construct_segment (if inode needs sync)
                  nilfs_segctor_sync  --&amp;gt; Attempt to synchronize with
                                          log writer thread
                           *** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;Fix this issue by changing nilfs_segctor_sync() so that the log writer
thread returns normally without synchronizing after it terminates, and by
forcing tasks that are already waiting to complete once after the thread
terminates.&lt;/p&gt;
&lt;p&gt;The skipped inode metadata flushout will then be processed together in the
subsequent cleanup work in nilfs_segctor_destroy().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-38582</guid>
    </item>
  </channel>
</rss>
