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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ bd3b963b273e247e13979f98812a6e4979b5c1e4 and < 0f709e08caffb41bbc9b38b9a4c1bd0769794007≥ bd3b963b273e247e13979f98812a6e4979b5c1e4 and < eab94a46560f68d4bcd15222701ced479f84f427≥ bd3b963b273e247e13979f98812a6e4979b5c1e4 and < 9ef603086c5b796fde1c7f22a17d0fc826ba54cb≥ bd3b963b273e247e13979f98812a6e4979b5c1e4 and < 9882601ee689975c1c0076ee65bf222a2a35e535≥ bd3b963b273e247e13979f98812a6e4979b5c1e4 and < 322cf639b0b7f137543072c55545adab782b3a25≥ bd3b963b273e247e13979f98812a6e4979b5c1e4 and < fdaaf45786dc8c17a72901021772520fceb18f8c≥ bd3b963b273e247e13979f98812a6e4979b5c1e4 and < 70e5b46beba64706430a87a6d516054225e8ac8a≥ bd3b963b273e247e13979f98812a6e4979b5c1e4 and < e4db04f7d3dbbe16680e0ded27ea2a65b10f766a and 1 moreversion 4.13 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.25%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/eab94a46560f68d4bcd15222701ced479f84f427
- git.kernel.org/stable/c/e4db04f7d3dbbe16680e0ded27ea2a65b10f766a
- git.kernel.org/stable/c/9882601ee689975c1c0076ee65bf222a2a35e535
- git.kernel.org/stable/c/fdaaf45786dc8c17a72901021772520fceb18f8c
- git.kernel.org/stable/c/0f709e08caffb41bbc9b38b9a4c1bd0769794007
- git.kernel.org/stable/c/322cf639b0b7f137543072c55545adab782b3a25
- git.kernel.org/stable/c/70e5b46beba64706430a87a6d516054225e8ac8a
- git.kernel.org/stable/c/9ef603086c5b796fde1c7f22a17d0fc826ba54cb
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-50845 is "ext4: fix inode leak in ext4_xattr_inode_create() on an error path", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.25% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.