<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T04:07:21.424828+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2026-80869</id>
    <title>CVE-2026-80869 — ntfs: bound the attribute-list entry in ntfs_read_inode_mount()</title>
    <updated>2026-10-07T04:07:21.445345+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 the attribute-list entry in ntfs_read_inode_mount()</p>
<p>The $MFT attribute-list walk in ntfs_read_inode_mount() validates each
entry only with "(u8 *)al_entry + 6 &gt; al_end" and
"(u8 *)al_entry + le16_to_cpu(al_entry-&gt;length) &gt; al_end", but then reads
al_entry-&gt;lowest_vcn (an __le64 at offset 8) and al_entry-&gt;mft_reference
(offset 16) -- fields beyond the 6 bytes proven in range. al_entry-&gt;length
is attacker-controlled and only required non-zero, so a short entry (e.g.
length 8) placed at the tail passes both checks while the lowest_vcn /
mft_reference reads fall past al_end.</p>
<p>al_end is ni-&gt;attr_list + attr_list_size (the on-disk size); the buffer is
kvzalloc(round_up(attr_list_size, SECTOR_SIZE)), so the sector rounding
usually absorbs the over-read -- but when attr_list_size is a multiple of
SECTOR_SIZE there is no slack and a crafted $MFT attribute list produces an
out-of-bounds read at mount time.</p>
<p>Validate the entry with ntfs_attr_list_entry_is_valid() (added in patch
1/3) before dereferencing it, matching the bound the other attribute-list
walks now use. The validator already requires the length to cover the fixed
header, which makes the separate "!al_entry-&gt;length" check redundant, so
drop it too.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-80869"/>
  </entry>
</feed>
