<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T03:12:09.020097+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-43127</id>
    <title>CVE-2026-43127 — ntfs3: fix circular locking dependency in run_unpack_ex</title>
    <updated>2026-10-04T03:12:09.443088+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ntfs3: fix circular locking dependency in run_unpack_ex</p>
<p>Syzbot reported a circular locking dependency between wnd-&gt;rw_lock
(sbi-&gt;used.bitmap) and ni-&gt;file.run_lock.</p>
<p>The deadlock scenario:
1. ntfs_extend_mft() takes ni-&gt;file.run_lock then wnd-&gt;rw_lock.
2. run_unpack_ex() takes wnd-&gt;rw_lock then tries to acquire
   ni-&gt;file.run_lock inside ntfs_refresh_zone().</p>
<p>This creates an AB-BA deadlock.</p>
<p>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-&gt;rw_lock.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-43127"/>
  </entry>
</feed>
