CVE-2022-50845

ext4: fix inode leak in ext4_xattr_inode_create() on an error path

N/A
Published: December 30, 2025 at 12:11 PM UTC
Updated: June 17, 2026 at 05:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.13 ≤ v < 4.14.3034.13 ≤ v < 4.19.2704.13 ≤ v < 5.10.1634.13 ≤ v < 5.15.874.13 ≤ v < 5.4.2294.13 ≤ v < 6.0.184.13 ≤ v < 6.1.44.13 ≤ v < 6.24.13bd3b963b273e247e13979f98812a6e4979b5c1e4
Vendor states this is fixed in 0f709e08caffb41bbc9b38b9a4c1bd0769794007 (fixed)
Vendor states this is fixed in 322cf639b0b7f137543072c55545adab782b3a25 (fixed)
Vendor states this is fixed in 70e5b46beba64706430a87a6d516054225e8ac8a (fixed)
Vendor states this is fixed in 9882601ee689975c1c0076ee65bf222a2a35e535 (fixed)
Vendor states this is fixed in 9ef603086c5b796fde1c7f22a17d0fc826ba54cb (fixed)
Vendor states this is fixed in e4db04f7d3dbbe16680e0ded27ea2a65b10f766a (fixed)
Vendor states this is fixed in eab94a46560f68d4bcd15222701ced479f84f427 (fixed)
Vendor states this is fixed in fdaaf45786dc8c17a72901021772520fceb18f8c (fixed)
Vendor states this is fixed in 4.13 (unaffected)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.87 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.18 (unaffected)
Vendor states this is fixed in 6.1.4 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card