<?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://cve.radiocsirt.org</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, 06 Oct 2026 02:53:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89779 — fs/ntfs3: validate ef-&gt;size covers the record's name and value</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-89779</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 ef-&amp;gt;size covers the record&amp;#39;s name and value&lt;/p&gt;
&lt;p&gt;When an EA record has a non-zero ef-&amp;gt;size, ntfs_read_ea() only checks
that the record fits in the remaining buffer (ea_size &amp;gt; bytes), not that
ef-&amp;gt;size is large enough to hold the record&amp;#39;s own name_len + 1 + elength.&lt;/p&gt;
&lt;p&gt;A crafted image can pass validation with, e.g., ef-&amp;gt;size = 24 but
elength = 0xffff. ntfs_get_ea() then trusts elength and copies it out of
the undersized record, reading past the kmalloc(info-&amp;gt;size) allocation
and leaking heap memory to userspace via getxattr():&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ntfs_get_ea (fs/ntfs3/xattr.c:302)
 Read of size 65535 at addr ffff888100794550 by task exploit
  __asan_memcpy (mm/kasan/shadow.c:105)
  ntfs_get_ea (fs/ntfs3/xattr.c:302)
  ntfs_getxattr (fs/ntfs3/xattr.c:848)
  __vfs_getxattr (fs/xattr.c:441)
  vfs_getxattr (fs/xattr.c:474)
  do_getxattr (fs/xattr.c:800)
  path_getxattrat (fs/xattr.c:868)
  do_syscall_64 (arch/x86/entry/syscall_64.c:94)&lt;/p&gt;
&lt;p&gt;The buggy address is located 80 bytes inside of
  allocated 84-byte region in cache kmalloc-96&lt;/p&gt;
&lt;p&gt;Compute the size the record needs and require ef-&amp;gt;size to cover it.&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 ef-&amp;gt;size covers the record&amp;#39;s name and value&lt;/p&gt;
&lt;p&gt;When an EA record has a non-zero ef-&amp;gt;size, ntfs_read_ea() only checks
that the record fits in the remaining buffer (ea_size &amp;gt; bytes), not that
ef-&amp;gt;size is large enough to hold the record&amp;#39;s own name_len + 1 + elength.&lt;/p&gt;
&lt;p&gt;A crafted image can pass validation with, e.g., ef-&amp;gt;size = 24 but
elength = 0xffff. ntfs_get_ea() then trusts elength and copies it out of
the undersized record, reading past the kmalloc(info-&amp;gt;size) allocation
and leaking heap memory to userspace via getxattr():&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ntfs_get_ea (fs/ntfs3/xattr.c:302)
 Read of size 65535 at addr ffff888100794550 by task exploit
  __asan_memcpy (mm/kasan/shadow.c:105)
  ntfs_get_ea (fs/ntfs3/xattr.c:302)
  ntfs_getxattr (fs/ntfs3/xattr.c:848)
  __vfs_getxattr (fs/xattr.c:441)
  vfs_getxattr (fs/xattr.c:474)
  do_getxattr (fs/xattr.c:800)
  path_getxattrat (fs/xattr.c:868)
  do_syscall_64 (arch/x86/entry/syscall_64.c:94)&lt;/p&gt;
&lt;p&gt;The buggy address is located 80 bytes inside of
  allocated 84-byte region in cache kmalloc-96&lt;/p&gt;
&lt;p&gt;Compute the size the record needs and require ef-&amp;gt;size to cover it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-89779</guid>
    </item>
  </channel>
</rss>
