LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50845: ext4: fix inode leak in ext4_xattr_inode_create() on an error path

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50845 is a Linux kernel ext4 filesystem bug. Under an error condition while setting extended attributes, ext4 can leak an inode and leave filesystem inconsistencies detected by fsck. The provided sources do not show remote exploitation, active exploitation, or a CVSS score.

Executive priority

Treat as a normal kernel maintenance item unless critical systems depend heavily on ext4 integrity. There is no sourced evidence of active exploitation, but filesystem inconsistency risk supports timely patching through standard change management.

Technical view

In ext4_xattr_inode_create(), if ext4_mark_inode_dirty() fails, the inode link count was not dropped. The CVE record says this can cause an inode leak, shown as an unattached zero-length inode during fsck.ext4. Kernel stable commits are referenced as the resolution.

Likely exposure

Systems using Linux kernels with ext4 filesystems may be exposed if running affected or unpatched kernel builds. Exposure is most relevant on hosts where local users or workloads can set extended attributes on ext4-backed storage.

Exploitation context

No KEV listing or cited source indicates active exploitation. The CVE description references setxattr with fault injection, suggesting a specific local filesystem error path rather than straightforward remote attack exposure.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. No CWE, CVSS, exploit status, or distribution-specific fixed package versions are provided in the bundle. Avoid assuming exploitability beyond the documented ext4 error path.

Mitigation direction

  • Check your Linux distribution’s advisory for CVE-2022-50845.
  • Update to a kernel package containing the referenced ext4 fix.
  • Prioritize ext4-heavy servers, shared Linux hosts, and storage-sensitive systems.
  • If no vendor advisory exists, track the linked kernel stable commits.

Validation and detection

  • Inventory Linux kernel versions across ext4-using systems.
  • Confirm whether vendor kernels include the ext4_xattr_inode_create fix.
  • Review fsck or storage monitoring for unexplained unattached inode errors.
  • Document affected hosts and planned kernel update windows.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50845 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbd3b963b273e247e13979f98812a6e4979b5c1e4, bd3b963b273e247e13979f98812a6e4979b5c1e4, bd3b963b273e247e13979f98812a6e4979b5c1e4, bd3b963b273e247e13979f98812a6e4979b5c1e4, bd3b963b273e247e13979f98812a6e4979b5c1e4, bd3b963b273e247e13979f98812a6e4979b5c1e4, bd3b963b273e247e13979f98812a6e4979b5c1e4, bd3b963b273e247e13979f98812a6e4979b5c1e4unaffected
LinuxLinux4.13, 0, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.87, 6.0.18, 6.1.4, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.