ext4: fix inode leak in ext4_xattr_inode_create() on an error path
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: fix inode leak in ext4_xattr_inode_create() on an error path There is issue as follows when do setxattr with inject fault: [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 Unattached inode 15 Connect to /lost+found? no Pass 5: Checking group summary information /dev/sda: ********** WARNING: Filesystem still has errors ********** /dev/sda: 15/655360 files (0.0% non-contiguous), 66755/2621440 blocks 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.13
References 8
git.kernel.org
- stable/c/0f709e08caffb41bbc9b38b9a4c1bd0769794007
- stable/c/eab94a46560f68d4bcd15222701ced479f84f427
- stable/c/9ef603086c5b796fde1c7f22a17d0fc826ba54cb
- stable/c/9882601ee689975c1c0076ee65bf222a2a35e535
- stable/c/322cf639b0b7f137543072c55545adab782b3a25
- stable/c/fdaaf45786dc8c17a72901021772520fceb18f8c
- stable/c/70e5b46beba64706430a87a6d516054225e8ac8a
- stable/c/e4db04f7d3dbbe16680e0ded27ea2a65b10f766a