<?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-10-02T05:13:09.031372+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-63815</id>
    <title>CVE-2026-63815 — f2fs: bound i_inline_xattr_size for non-inline-xattr inodes</title>
    <updated>2026-10-02T05:13:09.134162+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>f2fs: bound i_inline_xattr_size for non-inline-xattr inodes</p>
<p>When the flexible_inline_xattr feature is enabled, do_read_inode() loads
the on-disk i_inline_xattr_size unconditionally:</p>
<p>if (f2fs_sb_has_flexible_inline_xattr(sbi))
		fi-&gt;i_inline_xattr_size = le16_to_cpu(ri-&gt;i_inline_xattr_size);</p>
<p>but sanity_check_inode() only range-checks it when the inode also has the
FI_INLINE_XATTR flag set.  An inode that carries an inline dentry or inline
data but not FI_INLINE_XATTR -- the normal layout for an inline
directory -- therefore keeps a fully attacker-controlled
i_inline_xattr_size from a crafted image.</p>
<p>get_inline_xattr_addrs() returns that value with no flag gating, so it
feeds the inode geometry:</p>
<p>MAX_INLINE_DATA()  = 4 * (CUR_ADDRS_PER_INODE - i_inline_xattr_size - 1)
	NR_INLINE_DENTRY() = MAX_INLINE_DATA() * BITS_PER_BYTE / (...)
	addrs_per_page()   = CUR_ADDRS_PER_INODE - i_inline_xattr_size</p>
<p>A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY()
negative, so make_dentry_ptr_inline() sets d-&gt;max (int) to a negative
value.  The inline directory walk then compares an unsigned long bit_pos
against that negative d-&gt;max, which is promoted to a huge unsigned bound,
and reads far past the inline area:</p>
<p>while (bit_pos &lt; d-&gt;max)		/* fs/f2fs/dir.c */
		... test_bit_le(bit_pos, d-&gt;bitmap) / d-&gt;dentry[bit_pos] ...</p>
<p>Mounting a crafted image and reading such a directory triggers an
out-of-bound…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-63815"/>
  </entry>
</feed>
