<?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>Mon, 05 Oct 2026 08:33:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64533 — fs/ntfs3: validate lcns_follow in log_replay conversion</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64533</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 lcns_follow in log_replay conversion&lt;/p&gt;
&lt;p&gt;log_replay() converts DIR_PAGE_ENTRY_32 records into DIR_PAGE_ENTRY
records when replaying version 0 restart tables.&lt;/p&gt;
&lt;p&gt;During this conversion, the memmove() length is derived directly from
the on-disk lcns_follow field:&lt;/p&gt;
&lt;p&gt;memmove(&amp;amp;dp-&amp;gt;vcn, &amp;amp;dp0-&amp;gt;vcn_low,
		2 * sizeof(u64) +
				le32_to_cpu(dp-&amp;gt;lcns_follow) * sizeof(u64));&lt;/p&gt;
&lt;p&gt;check_rstbl() validates restart table structure, but does not constrain
per-entry lcns_follow values relative to the entry size. A malformed
filesystem image can provide an oversized lcns_follow value, causing
the conversion memmove() to access memory beyond the bounds of the
allocated restart table buffer.&lt;/p&gt;
&lt;p&gt;The same field is later used to bound iteration over page_lcns[],
so validating lcns_follow during conversion also prevents downstream
out-of-bounds access from the same malformed metadata.&lt;/p&gt;
&lt;p&gt;Compute the maximum valid lcns_follow from the already-validated
restart table entry size and reject entries that exceed this bound.
Reuse the existing t16/t32 scratch variables already declared in
log_replay() to avoid introducing new declarations.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: fixed the conflicts]&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 lcns_follow in log_replay conversion&lt;/p&gt;
&lt;p&gt;log_replay() converts DIR_PAGE_ENTRY_32 records into DIR_PAGE_ENTRY
records when replaying version 0 restart tables.&lt;/p&gt;
&lt;p&gt;During this conversion, the memmove() length is derived directly from
the on-disk lcns_follow field:&lt;/p&gt;
&lt;p&gt;memmove(&amp;amp;dp-&amp;gt;vcn, &amp;amp;dp0-&amp;gt;vcn_low,
		2 * sizeof(u64) +
				le32_to_cpu(dp-&amp;gt;lcns_follow) * sizeof(u64));&lt;/p&gt;
&lt;p&gt;check_rstbl() validates restart table structure, but does not constrain
per-entry lcns_follow values relative to the entry size. A malformed
filesystem image can provide an oversized lcns_follow value, causing
the conversion memmove() to access memory beyond the bounds of the
allocated restart table buffer.&lt;/p&gt;
&lt;p&gt;The same field is later used to bound iteration over page_lcns[],
so validating lcns_follow during conversion also prevents downstream
out-of-bounds access from the same malformed metadata.&lt;/p&gt;
&lt;p&gt;Compute the maximum valid lcns_follow from the already-validated
restart table entry size and reject entries that exceed this bound.
Reuse the existing t16/t32 scratch variables already declared in
log_replay() to avoid introducing new declarations.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: fixed the conflicts]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64533</guid>
    </item>
  </channel>
</rss>
