ext4: fix inode leak in ext4_xattr_inode_create() on an error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bd3b963b273e247e13979f98812a6e4979b5c1e4 · < fdaaf45786dc8c17a72901021772520fceb18f8c| No fix yet |
| Linux Linux |
|
|
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
From the CVE record · Linux
The Linux kernel's ext4_xattr_inode_create() can leak an inode if ext4_mark_inode_dirty() fails during setxattr. The reported case requires a local setxattr operation and an injected fault, and leaves filesystem errors visible to fsck. The input does not establish whether authentication is required beyond the ability to perform setxattr.
Engineers running Linux systems with ext4 filesystems should check their kernel versions; affected versions are not specified.