<?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-09-30T23:03:52.270797+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-2022-50845</id>
    <title>CVE-2022-50845 — ext4: fix inode leak in ext4_xattr_inode_create() on an error path</title>
    <updated>2026-09-30T23:03:53.216988+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>ext4: fix inode leak in ext4_xattr_inode_create() on an error path</p>
<p>There is issue as follows when do setxattr with inject fault:</p>
<p>[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</p>
<p>Unattached inode 15
Connect to /lost+found? no</p>
<p>Pass 5: Checking group summary information</p>
<p>/dev/sda: ********** WARNING: Filesystem still has errors **********</p>
<p>/dev/sda: 15/655360 files (0.0% non-contiguous), 66755/2621440 blocks</p>
<p>This occurs in 'ext4_xattr_inode_create()'. If 'ext4_mark_inode_dirty()'
fails, dropping i_nlink of the inode is needed. Or will lead to inode leak.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-50845"/>
  </entry>
</feed>
