<?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>Sun, 04 Oct 2026 05:12:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43127 — ntfs3: fix circular locking dependency in run_unpack_ex</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43127</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;ntfs3: fix circular locking dependency in run_unpack_ex&lt;/p&gt;
&lt;p&gt;Syzbot reported a circular locking dependency between wnd-&amp;gt;rw_lock
(sbi-&amp;gt;used.bitmap) and ni-&amp;gt;file.run_lock.&lt;/p&gt;
&lt;p&gt;The deadlock scenario:
1. ntfs_extend_mft() takes ni-&amp;gt;file.run_lock then wnd-&amp;gt;rw_lock.
2. run_unpack_ex() takes wnd-&amp;gt;rw_lock then tries to acquire
   ni-&amp;gt;file.run_lock inside ntfs_refresh_zone().&lt;/p&gt;
&lt;p&gt;This creates an AB-BA deadlock.&lt;/p&gt;
&lt;p&gt;Fix this by using down_read_trylock() instead of down_read() when
acquiring run_lock in run_unpack_ex(). If the lock is contended,
skip ntfs_refresh_zone() - the MFT zone will be refreshed on the
next MFT operation. This breaks the circular dependency since we
never block waiting for run_lock while holding wnd-&amp;gt;rw_lock.&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;ntfs3: fix circular locking dependency in run_unpack_ex&lt;/p&gt;
&lt;p&gt;Syzbot reported a circular locking dependency between wnd-&amp;gt;rw_lock
(sbi-&amp;gt;used.bitmap) and ni-&amp;gt;file.run_lock.&lt;/p&gt;
&lt;p&gt;The deadlock scenario:
1. ntfs_extend_mft() takes ni-&amp;gt;file.run_lock then wnd-&amp;gt;rw_lock.
2. run_unpack_ex() takes wnd-&amp;gt;rw_lock then tries to acquire
   ni-&amp;gt;file.run_lock inside ntfs_refresh_zone().&lt;/p&gt;
&lt;p&gt;This creates an AB-BA deadlock.&lt;/p&gt;
&lt;p&gt;Fix this by using down_read_trylock() instead of down_read() when
acquiring run_lock in run_unpack_ex(). If the lock is contended,
skip ntfs_refresh_zone() - the MFT zone will be refreshed on the
next MFT operation. This breaks the circular dependency since we
never block waiting for run_lock while holding wnd-&amp;gt;rw_lock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43127</guid>
    </item>
  </channel>
</rss>
