<?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>Sat, 03 Oct 2026 23:15:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53029 — fs/ntfs3: prevent uninitialized lcn caused by zero len</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53029</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;fs/ntfs3: prevent uninitialized lcn caused by zero len&lt;/p&gt;
&lt;p&gt;syzbot reported a uninit-value in ntfs_iomap_begin [1].&lt;/p&gt;
&lt;p&gt;Since runs was not touched yet, run_lookup_entry() immediately fails
and returns false, which makes the value of &amp;#34;*len&amp;#34; 0.
Simultaneously, the new value and err value are also 0, causing the
logic in attr_data_get_block_locked() to jump directly to ok, ultimately
resulting in *lcn being triggered before it is set [1].&lt;/p&gt;
&lt;p&gt;In ntfs_iomap_begin(), the check for a 0 value in clen is moved forward
to before updating lcn to avoid this [1].&lt;/p&gt;
&lt;p&gt;[1]
BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825
 ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825
 iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110&lt;/p&gt;
&lt;p&gt;Local variable lcn created at:
 ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786&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;fs/ntfs3: prevent uninitialized lcn caused by zero len&lt;/p&gt;
&lt;p&gt;syzbot reported a uninit-value in ntfs_iomap_begin [1].&lt;/p&gt;
&lt;p&gt;Since runs was not touched yet, run_lookup_entry() immediately fails
and returns false, which makes the value of &amp;#34;*len&amp;#34; 0.
Simultaneously, the new value and err value are also 0, causing the
logic in attr_data_get_block_locked() to jump directly to ok, ultimately
resulting in *lcn being triggered before it is set [1].&lt;/p&gt;
&lt;p&gt;In ntfs_iomap_begin(), the check for a 0 value in clen is moved forward
to before updating lcn to avoid this [1].&lt;/p&gt;
&lt;p&gt;[1]
BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825
 ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825
 iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110&lt;/p&gt;
&lt;p&gt;Local variable lcn created at:
 ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53029</guid>
    </item>
  </channel>
</rss>
