<?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>Sun, 04 Oct 2026 14:31:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-63815</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-63815</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-63815</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0930 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0930</link>
      <description>certfr-2026-avi-0930</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0930</guid>
    </item>
    <item>
      <title>EUVD-2026-353136</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353136</link>
      <description>EUVD-2026-353136</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353136</guid>
    </item>
    <item>
      <title>fkie_cve-2026-63815</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-63815</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: bound i_inline_xattr_size for non-inline-xattr inodes&lt;/p&gt;
&lt;p&gt;When the flexible_inline_xattr feature is enabled, do_read_inode() loads
the on-disk i_inline_xattr_size unconditionally:&lt;/p&gt;
&lt;p&gt;if (f2fs_sb_has_flexible_inline_xattr(sbi))
		fi-&amp;gt;i_inline_xattr_size = le16_to_cpu(ri-&amp;gt;i_inline_xattr_size);&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;get_inline_xattr_addrs() returns that value with no flag gating, so it
feeds the inode geometry:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY()
negative, so make_dentry_ptr_inline() sets d-&amp;gt;max (int) to a negative
value.  The inline directory walk then compares an unsigned long bit_pos
against that negative d-&amp;gt;max, which is promoted to a huge unsigned bound,
and reads far past the inline area:&lt;/p&gt;
&lt;p&gt;while (bit_pos &amp;lt; d-&amp;gt;max)		/* fs/f2fs/dir.c */
		... test_bit_le(bit_pos, d-&amp;gt;bitmap) / d-&amp;gt;dentry[bit_pos] ...&lt;/p&gt;
&lt;p&gt;Mounting a crafted image and reading such a directory triggers an
out-of-bound…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: bound i_inline_xattr_size for non-inline-xattr inodes&lt;/p&gt;
&lt;p&gt;When the flexible_inline_xattr feature is enabled, do_read_inode() loads
the on-disk i_inline_xattr_size unconditionally:&lt;/p&gt;
&lt;p&gt;if (f2fs_sb_has_flexible_inline_xattr(sbi))
		fi-&amp;gt;i_inline_xattr_size = le16_to_cpu(ri-&amp;gt;i_inline_xattr_size);&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;get_inline_xattr_addrs() returns that value with no flag gating, so it
feeds the inode geometry:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY()
negative, so make_dentry_ptr_inline() sets d-&amp;gt;max (int) to a negative
value.  The inline directory walk then compares an unsigned long bit_pos
against that negative d-&amp;gt;max, which is promoted to a huge unsigned bound,
and reads far past the inline area:&lt;/p&gt;
&lt;p&gt;while (bit_pos &amp;lt; d-&amp;gt;max)		/* fs/f2fs/dir.c */
		... test_bit_le(bit_pos, d-&amp;gt;bitmap) / d-&amp;gt;dentry[bit_pos] ...&lt;/p&gt;
&lt;p&gt;Mounting a crafted image and reading such a directory triggers an
out-of-bound…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-63815</guid>
    </item>
    <item>
      <title>GHSA-7mq9-8547-cp53</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7mq9-8547-cp53</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: bound i_inline_xattr_size for non-inline-xattr inodes&lt;/p&gt;
&lt;p&gt;When the flexible_inline_xattr feature is enabled, do_read_inode() loads
the on-disk i_inline_xattr_size unconditionally:&lt;/p&gt;
&lt;p&gt;if (f2fs_sb_has_flexible_inline_xattr(sbi))
		fi-&amp;gt;i_inline_xattr_size = le16_to_cpu(ri-&amp;gt;i_inline_xattr_size);&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;get_inline_xattr_addrs() returns that value with no flag gating, so it
feeds the inode geometry:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY()
negative, so make_dentry_ptr_inline() sets d-&amp;gt;max (int) to a negative
value.  The inline directory walk then compares an unsigned long bit_pos
against that negative d-&amp;gt;max, which is promoted to a huge unsigned bound,
and reads far past the inline area:&lt;/p&gt;
&lt;p&gt;while (bit_pos &amp;lt; d-&amp;gt;max)		/* fs/f2fs/dir.c */
		... test_bit_le(bit_pos, d-&amp;gt;bitmap) / d-&amp;gt;dentry[bit_pos] ...&lt;/p&gt;
&lt;p&gt;Mounting a crafted image and reading such a directory triggers an
out-of-bound…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: bound i_inline_xattr_size for non-inline-xattr inodes&lt;/p&gt;
&lt;p&gt;When the flexible_inline_xattr feature is enabled, do_read_inode() loads
the on-disk i_inline_xattr_size unconditionally:&lt;/p&gt;
&lt;p&gt;if (f2fs_sb_has_flexible_inline_xattr(sbi))
		fi-&amp;gt;i_inline_xattr_size = le16_to_cpu(ri-&amp;gt;i_inline_xattr_size);&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;get_inline_xattr_addrs() returns that value with no flag gating, so it
feeds the inode geometry:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY()
negative, so make_dentry_ptr_inline() sets d-&amp;gt;max (int) to a negative
value.  The inline directory walk then compares an unsigned long bit_pos
against that negative d-&amp;gt;max, which is promoted to a huge unsigned bound,
and reads far past the inline area:&lt;/p&gt;
&lt;p&gt;while (bit_pos &amp;lt; d-&amp;gt;max)		/* fs/f2fs/dir.c */
		... test_bit_le(bit_pos, d-&amp;gt;bitmap) / d-&amp;gt;dentry[bit_pos] ...&lt;/p&gt;
&lt;p&gt;Mounting a crafted image and reading such a directory triggers an
out-of-bound…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7mq9-8547-cp53</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-63815 — f2fs: bound i_inline_xattr_size for non-inline-xattr inodes</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-63815</link>
      <description>msrc_CVE-2026-63815</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-63815</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11339-1 — kernel-devel-7.1.4-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.4-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.4-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63815</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63815</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: bound i_inline_xattr_size for non-inline-xattr inodes When the flexible_inline_xattr feature is enabled, do_read_inode() loads the on-disk i_inline_xattr_size unconditionally: 	if (f2fs_sb_has_flexible_inline_xattr(sbi)) 		fi-&amp;gt;i_inline_xattr_size = le16_to_cpu(ri-&amp;gt;i_inline_xattr_size); 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. get_inline_xattr_addrs() returns that value with no flag gating, so it feeds the inode geometry: 	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 A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY() negative, so make_dentry_ptr_inline() sets d-&amp;gt;max (int) to a negative value.  The inline directory walk then compares an unsigned long bit_pos against that negative d-&amp;gt;max, which is promoted to a huge unsigned bound, and reads far past the inline area: 	while (bit_pos &amp;lt; d-&amp;gt;max)		/* fs/f2fs/dir.c */ 		... test_bit_le(bit_pos, d-&amp;gt;bitmap) / d-&amp;gt;dentry[bit_pos] ... Mounting a crafted image and reading such a directory triggers an out-of-bounds read in…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: bound i_inline_xattr_size for non-inline-xattr inodes When the flexible_inline_xattr feature is enabled, do_read_inode() loads the on-disk i_inline_xattr_size unconditionally: 	if (f2fs_sb_has_flexible_inline_xattr(sbi)) 		fi-&amp;gt;i_inline_xattr_size = le16_to_cpu(ri-&amp;gt;i_inline_xattr_size); 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. get_inline_xattr_addrs() returns that value with no flag gating, so it feeds the inode geometry: 	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 A large i_inline_xattr_size drives MAX_INLINE_DATA() and NR_INLINE_DENTRY() negative, so make_dentry_ptr_inline() sets d-&amp;gt;max (int) to a negative value.  The inline directory walk then compares an unsigned long bit_pos against that negative d-&amp;gt;max, which is promoted to a huge unsigned bound, and reads far past the inline area: 	while (bit_pos &amp;lt; d-&amp;gt;max)		/* fs/f2fs/dir.c */ 		... test_bit_le(bit_pos, d-&amp;gt;bitmap) / d-&amp;gt;dentry[bit_pos] ... Mounting a crafted image and reading such a directory triggers an out-of-bounds read in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63815</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
