<?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>Thu, 01 Oct 2026 17:00:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64432 — fs/ntfs3: validate Dirty Page Table capacity in log_replay copy_lcns</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64432</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: validate Dirty Page Table capacity in log_replay copy_lcns&lt;/p&gt;
&lt;p&gt;In the analysis pass of $LogFile journal replay, log_replay() copies
LCNs from each action log record into an existing Dirty Page Table
(DPT) entry without bounding the destination index. A crafted NTFS
image with DPT entry lcns_follow=1 and an action log record with
lcns_follow=2 produces a kernel slab out-of-bounds write at mount
time:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in log_replay+0x654c/0xdb60
  Write of size 8 at addr ffff8880095e1040 by task mount&lt;/p&gt;
&lt;p&gt;Two attacker-controlled fields can drive j+i past the allocated
page_lcns[] array:&lt;/p&gt;
&lt;p&gt;1. dp-&amp;gt;lcns_follow (capacity) can be smaller than lrh-&amp;gt;lcns_follow.
  2. lrh-&amp;gt;target_vcn may be smaller than dp-&amp;gt;vcn, making the u64
     subtraction wrap to a huge size_t.&lt;/p&gt;
&lt;p&gt;Validate target VCN delta and per-record LCN count against the
DPT entry capacity, bail via the existing out: cleanup label with
-EINVAL.&lt;/p&gt;
&lt;p&gt;This mirrors the bounds-check pattern added in commit b2bc7c44ed17
(&amp;#34;fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot&amp;#34;)
and commit 0ca0485e4b2e (&amp;#34;fs/ntfs3: validate rec-&amp;gt;used in
journal-replay file record check&amp;#34;).&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: validate Dirty Page Table capacity in log_replay copy_lcns&lt;/p&gt;
&lt;p&gt;In the analysis pass of $LogFile journal replay, log_replay() copies
LCNs from each action log record into an existing Dirty Page Table
(DPT) entry without bounding the destination index. A crafted NTFS
image with DPT entry lcns_follow=1 and an action log record with
lcns_follow=2 produces a kernel slab out-of-bounds write at mount
time:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in log_replay+0x654c/0xdb60
  Write of size 8 at addr ffff8880095e1040 by task mount&lt;/p&gt;
&lt;p&gt;Two attacker-controlled fields can drive j+i past the allocated
page_lcns[] array:&lt;/p&gt;
&lt;p&gt;1. dp-&amp;gt;lcns_follow (capacity) can be smaller than lrh-&amp;gt;lcns_follow.
  2. lrh-&amp;gt;target_vcn may be smaller than dp-&amp;gt;vcn, making the u64
     subtraction wrap to a huge size_t.&lt;/p&gt;
&lt;p&gt;Validate target VCN delta and per-record LCN count against the
DPT entry capacity, bail via the existing out: cleanup label with
-EINVAL.&lt;/p&gt;
&lt;p&gt;This mirrors the bounds-check pattern added in commit b2bc7c44ed17
(&amp;#34;fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot&amp;#34;)
and commit 0ca0485e4b2e (&amp;#34;fs/ntfs3: validate rec-&amp;gt;used in
journal-replay file record check&amp;#34;).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64432</guid>
    </item>
  </channel>
</rss>
