<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T09:31:49.699908+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-98136</id>
    <title>CVE-2026-98136 — ntfs: bound $AttrDef table walk to the loaded table size</title>
    <updated>2026-09-28T09:31:49.701657+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ntfs: bound $AttrDef table walk to the loaded table size</p>
<p>ntfs_attr_find_in_attrdef() walks the in-memory $AttrDef table, but the
loop condition bounds only the start of each entry, not the whole entry:</p>
<p>for (ad = vol-&gt;attrdef; (u8 *)ad - (u8 *)vol-&gt;attrdef &lt;
			vol-&gt;attrdef_size &amp;&amp; ad-&gt;type; ++ad)</p>
<p>struct attr_def is 160 bytes; the guard reads ad-&gt;type at offset 128 and
the loop body reads further fields. vol-&gt;attrdef is kvzalloc(i_size),
where i_size is the on-disk $AttrDef data size, checked in
load_and_init_attrdef() only as 0 &lt; i_size &lt;= 0x7fffffff. A volume whose
$AttrDef data size is smaller than one entry (e.g. 120 bytes) makes the
read of ad-&gt;type run past the allocation. Creating a file reaches this
through ntfs_attr_size_bounds_check() and reads out of bounds:</p>
<p>BUG: KASAN: slab-out-of-bounds in ntfs_attr_find_in_attrdef+0x66/0xa0
  Read of size 4 at addr ffff888005833280 by task init/1
   ntfs_attr_find_in_attrdef
   ntfs_attr_size_bounds_check
   ntfs_attr_can_be_non_resident
   ntfs_attr_add</p>
<p>Require the whole entry to lie within attrdef_size in the loop guard, and
reject at mount a $AttrDef too small to hold one attr_def entry.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-98136"/>
  </entry>
</feed>
