<?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>Wed, 30 Sep 2026 23:23:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45935 — fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-45935</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: Fix slab-out-of-bounds read in DeleteIndexEntryRoot&lt;/p&gt;
&lt;p&gt;In the &amp;#39;DeleteIndexEntryRoot&amp;#39; case of the &amp;#39;do_action&amp;#39; function, the
entry size (&amp;#39;esize&amp;#39;) is retrieved from the log record without adequate
bounds checking.&lt;/p&gt;
&lt;p&gt;Specifically, the code calculates the end of the entry (&amp;#39;e2&amp;#39;) using:
    e2 = Add2Ptr(e1, esize);&lt;/p&gt;
&lt;p&gt;It then calculates the size for memmove using &amp;#39;PtrOffset(e2, ...)&amp;#39;,
which subtracts the end pointer from the buffer limit. If &amp;#39;esize&amp;#39; is
maliciously large, &amp;#39;e2&amp;#39; exceeds the used buffer size. This results in
a negative offset which, when cast to size_t for memmove, interprets
as a massive unsigned integer, leading to a heap buffer overflow.&lt;/p&gt;
&lt;p&gt;This commit adds a check to ensure that the entry size (&amp;#39;esize&amp;#39;) strictly
fits within the remaining used space of the index header before performing
memory operations.&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: Fix slab-out-of-bounds read in DeleteIndexEntryRoot&lt;/p&gt;
&lt;p&gt;In the &amp;#39;DeleteIndexEntryRoot&amp;#39; case of the &amp;#39;do_action&amp;#39; function, the
entry size (&amp;#39;esize&amp;#39;) is retrieved from the log record without adequate
bounds checking.&lt;/p&gt;
&lt;p&gt;Specifically, the code calculates the end of the entry (&amp;#39;e2&amp;#39;) using:
    e2 = Add2Ptr(e1, esize);&lt;/p&gt;
&lt;p&gt;It then calculates the size for memmove using &amp;#39;PtrOffset(e2, ...)&amp;#39;,
which subtracts the end pointer from the buffer limit. If &amp;#39;esize&amp;#39; is
maliciously large, &amp;#39;e2&amp;#39; exceeds the used buffer size. This results in
a negative offset which, when cast to size_t for memmove, interprets
as a massive unsigned integer, leading to a heap buffer overflow.&lt;/p&gt;
&lt;p&gt;This commit adds a check to ensure that the entry size (&amp;#39;esize&amp;#39;) strictly
fits within the remaining used space of the index header before performing
memory operations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-45935</guid>
    </item>
  </channel>
</rss>
