<?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://vulnerability.circl.lu</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, 29 Sep 2026 04:55:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40190 — ext4: guard against EA inode refcount underflow in xattr update</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40190</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;ext4: guard against EA inode refcount underflow in xattr update&lt;/p&gt;
&lt;p&gt;syzkaller found a path where ext4_xattr_inode_update_ref() reads an EA
inode refcount that is already &amp;lt;= 0 and then applies ref_change (often
-1). That lets the refcount underflow and we proceed with a bogus value,
triggering errors like:&lt;/p&gt;
&lt;p&gt;EXT4-fs error: EA inode &amp;lt;n&amp;gt; ref underflow: ref_count=-1 ref_change=-1
  EXT4-fs warning: ea_inode dec ref err=-117&lt;/p&gt;
&lt;p&gt;Make the invariant explicit: if the current refcount is non-positive,
treat this as on-disk corruption, emit ext4_error_inode(), and fail the
operation with -EFSCORRUPTED instead of updating the refcount. Delete the
WARN_ONCE() as negative refcounts are now impossible; keep error reporting
in ext4_error_inode().&lt;/p&gt;
&lt;p&gt;This prevents the underflow and the follow-on orphan/cleanup churn.&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;ext4: guard against EA inode refcount underflow in xattr update&lt;/p&gt;
&lt;p&gt;syzkaller found a path where ext4_xattr_inode_update_ref() reads an EA
inode refcount that is already &amp;lt;= 0 and then applies ref_change (often
-1). That lets the refcount underflow and we proceed with a bogus value,
triggering errors like:&lt;/p&gt;
&lt;p&gt;EXT4-fs error: EA inode &amp;lt;n&amp;gt; ref underflow: ref_count=-1 ref_change=-1
  EXT4-fs warning: ea_inode dec ref err=-117&lt;/p&gt;
&lt;p&gt;Make the invariant explicit: if the current refcount is non-positive,
treat this as on-disk corruption, emit ext4_error_inode(), and fail the
operation with -EFSCORRUPTED instead of updating the refcount. Delete the
WARN_ONCE() as negative refcounts are now impossible; keep error reporting
in ext4_error_inode().&lt;/p&gt;
&lt;p&gt;This prevents the underflow and the follow-on orphan/cleanup churn.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40190</guid>
    </item>
  </channel>
</rss>
