<?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 06:29:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53608 — nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53608</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 UAF of struct nilfs_sc_info in nilfs_segctor_thread()&lt;/p&gt;
&lt;p&gt;The finalization of nilfs_segctor_thread() can race with
nilfs_segctor_kill_thread() which terminates that thread, potentially
causing a use-after-free BUG as KASAN detected.&lt;/p&gt;
&lt;p&gt;At the end of nilfs_segctor_thread(), it assigns NULL to &amp;#34;sc_task&amp;#34; member
of &amp;#34;struct nilfs_sc_info&amp;#34; to indicate the thread has finished, and then
notifies nilfs_segctor_kill_thread() of this using waitqueue
&amp;#34;sc_wait_task&amp;#34; on the struct nilfs_sc_info.&lt;/p&gt;
&lt;p&gt;However, here, immediately after the NULL assignment to &amp;#34;sc_task&amp;#34;, it is
possible that nilfs_segctor_kill_thread() will detect it and return to
continue the deallocation, freeing the nilfs_sc_info structure before the
thread does the notification.&lt;/p&gt;
&lt;p&gt;This fixes the issue by protecting the NULL assignment to &amp;#34;sc_task&amp;#34; and
its notification, with spinlock &amp;#34;sc_state_lock&amp;#34; of the struct
nilfs_sc_info.  Since nilfs_segctor_kill_thread() does a final check to
see if &amp;#34;sc_task&amp;#34; is NULL with &amp;#34;sc_state_lock&amp;#34; locked, this can eliminate
the race.&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 UAF of struct nilfs_sc_info in nilfs_segctor_thread()&lt;/p&gt;
&lt;p&gt;The finalization of nilfs_segctor_thread() can race with
nilfs_segctor_kill_thread() which terminates that thread, potentially
causing a use-after-free BUG as KASAN detected.&lt;/p&gt;
&lt;p&gt;At the end of nilfs_segctor_thread(), it assigns NULL to &amp;#34;sc_task&amp;#34; member
of &amp;#34;struct nilfs_sc_info&amp;#34; to indicate the thread has finished, and then
notifies nilfs_segctor_kill_thread() of this using waitqueue
&amp;#34;sc_wait_task&amp;#34; on the struct nilfs_sc_info.&lt;/p&gt;
&lt;p&gt;However, here, immediately after the NULL assignment to &amp;#34;sc_task&amp;#34;, it is
possible that nilfs_segctor_kill_thread() will detect it and return to
continue the deallocation, freeing the nilfs_sc_info structure before the
thread does the notification.&lt;/p&gt;
&lt;p&gt;This fixes the issue by protecting the NULL assignment to &amp;#34;sc_task&amp;#34; and
its notification, with spinlock &amp;#34;sc_state_lock&amp;#34; of the struct
nilfs_sc_info.  Since nilfs_segctor_kill_thread() does a final check to
see if &amp;#34;sc_task&amp;#34; is NULL with &amp;#34;sc_state_lock&amp;#34; locked, this can eliminate
the race.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53608</guid>
    </item>
  </channel>
</rss>
