<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-30T05:03:19.454878+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-99107</id>
    <title>CVE-2026-99107 — ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize</title>
    <updated>2026-10-30T05:03:19.457108+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: fix incorrect MFT record pointer passed to ntfs_attr_record_resize</p>
<p>ntfs_new_attr_flags() passes the wrong MFT record to ntfs_attr_record_resize().
When the attribute is in an extent record, ctx-&gt;mrec points to the extent
but the function receives the base record pointer m, causing incorrect
size calculations in memmove.</p>
<p>Fix by passing ctx-&gt;mrec (the actual MFT record containing the attribute)
instead of m (the base MFT record) to ntfs_attr_record_resize().</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99107"/>
  </entry>
</feed>
