<?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>Wed, 30 Sep 2026 23:03:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50845 — ext4: fix inode leak in ext4_xattr_inode_create() on an error path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50845</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: fix inode leak in ext4_xattr_inode_create() on an error path&lt;/p&gt;
&lt;p&gt;There is issue as follows when do setxattr with inject fault:&lt;/p&gt;
&lt;p&gt;[localhost]# fsck.ext4  -fn  /dev/sda
e2fsck 1.46.6-rc1 (12-Sep-2022)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached zero-length inode 15.  Clear? no&lt;/p&gt;
&lt;p&gt;Unattached inode 15
Connect to /lost+found? no&lt;/p&gt;
&lt;p&gt;Pass 5: Checking group summary information&lt;/p&gt;
&lt;p&gt;/dev/sda: ********** WARNING: Filesystem still has errors **********&lt;/p&gt;
&lt;p&gt;/dev/sda: 15/655360 files (0.0% non-contiguous), 66755/2621440 blocks&lt;/p&gt;
&lt;p&gt;This occurs in &amp;#39;ext4_xattr_inode_create()&amp;#39;. If &amp;#39;ext4_mark_inode_dirty()&amp;#39;
fails, dropping i_nlink of the inode is needed. Or will lead to inode leak.&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: fix inode leak in ext4_xattr_inode_create() on an error path&lt;/p&gt;
&lt;p&gt;There is issue as follows when do setxattr with inject fault:&lt;/p&gt;
&lt;p&gt;[localhost]# fsck.ext4  -fn  /dev/sda
e2fsck 1.46.6-rc1 (12-Sep-2022)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached zero-length inode 15.  Clear? no&lt;/p&gt;
&lt;p&gt;Unattached inode 15
Connect to /lost+found? no&lt;/p&gt;
&lt;p&gt;Pass 5: Checking group summary information&lt;/p&gt;
&lt;p&gt;/dev/sda: ********** WARNING: Filesystem still has errors **********&lt;/p&gt;
&lt;p&gt;/dev/sda: 15/655360 files (0.0% non-contiguous), 66755/2621440 blocks&lt;/p&gt;
&lt;p&gt;This occurs in &amp;#39;ext4_xattr_inode_create()&amp;#39;. If &amp;#39;ext4_mark_inode_dirty()&amp;#39;
fails, dropping i_nlink of the inode is needed. Or will lead to inode leak.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50845</guid>
    </item>
  </channel>
</rss>
