<?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>Tue, 29 Sep 2026 15:38:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80673 — ntfs: bound the look-ahead attribute-list entry in ntfs_external_attr_find()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80673</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;ntfs: bound the look-ahead attribute-list entry in ntfs_external_attr_find()&lt;/p&gt;
&lt;p&gt;When resolving an attribute lookup with a non-zero @lowest_vcn,
ntfs_external_attr_find() peeks at the next $ATTRIBUTE_LIST entry to
decide whether to keep searching, but bounds that not-yet-validated
entry only with &amp;#34;(u8 *)next_al_entry + 6 &amp;lt; al_end&amp;#34; (which proves just
bytes 0..6 are in range) and &amp;#34;(u8 *)next_al_entry + length &amp;lt;= al_end&amp;#34;
with an attacker-controlled, non-8-aligned length. It then reads
next_al_entry-&amp;gt;lowest_vcn (an __le64 at offset 8) and the name at
next_al_entry-&amp;gt;name_offset, both of which can lie past al_end -- the
exact end of the kvmalloc&amp;#39;d attribute-list buffer (allocated at the
on-disk attr_list_size, no rounding). A crafted on-disk $ATTRIBUTE_LIST
whose last entry sits a few bytes before al_end therefore yields a slab
out-of-bounds read when the inode is read.&lt;/p&gt;
&lt;p&gt;Validate the look-ahead entry with ntfs_attr_list_entry_is_valid() (added
in patch 1/3) before dereferencing lowest_vcn and the name, so the same
fixed-header, length and name bounds the main attribute-list walk uses now
guard this read too.&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;ntfs: bound the look-ahead attribute-list entry in ntfs_external_attr_find()&lt;/p&gt;
&lt;p&gt;When resolving an attribute lookup with a non-zero @lowest_vcn,
ntfs_external_attr_find() peeks at the next $ATTRIBUTE_LIST entry to
decide whether to keep searching, but bounds that not-yet-validated
entry only with &amp;#34;(u8 *)next_al_entry + 6 &amp;lt; al_end&amp;#34; (which proves just
bytes 0..6 are in range) and &amp;#34;(u8 *)next_al_entry + length &amp;lt;= al_end&amp;#34;
with an attacker-controlled, non-8-aligned length. It then reads
next_al_entry-&amp;gt;lowest_vcn (an __le64 at offset 8) and the name at
next_al_entry-&amp;gt;name_offset, both of which can lie past al_end -- the
exact end of the kvmalloc&amp;#39;d attribute-list buffer (allocated at the
on-disk attr_list_size, no rounding). A crafted on-disk $ATTRIBUTE_LIST
whose last entry sits a few bytes before al_end therefore yields a slab
out-of-bounds read when the inode is read.&lt;/p&gt;
&lt;p&gt;Validate the look-ahead entry with ntfs_attr_list_entry_is_valid() (added
in patch 1/3) before dereferencing lowest_vcn and the name, so the same
fixed-header, length and name bounds the main attribute-list walk uses now
guard this read too.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80673</guid>
    </item>
  </channel>
</rss>
