Linux Kernel up to 6.0.0 inode_init_always use after free

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.0.0. This vulnerability affects the function inode_init_always. The manipulation results in use after free.
This vulnerability is known as CVE-2022-50367. No exploit is available.
You should upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 6.0.0. It has been classified as critical. Affected is the function inode_init_always. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: fs: fix UAF/GPF bug in nilfs_mdt_destroy In alloc_inode, inode_init_always() could return -ENOMEM if security_inode_alloc() fails, which causes inode->i_private uninitialized. Then nilfs_is_metadata_file_inode() returns true and nilfs_free_inode() wrongly calls nilfs_mdt_destroy(), which frees the uninitialized inode->i_private and leads to crashes(e.g., UAF/GPF). Fix this by moving security_inode_alloc just prior to this_cpu_inc(nr_inodes)
The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2022-50367 since 09/17/2025. The exploitability is told to be easy. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 12/27/2025).
The vulnerability scanner Nessus provides a plugin with the ID 265645 (Linux Distros Unpatched Vulnerability : CVE-2022-50367), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.9.331, 4.14.296, 4.19.262, 5.4.218, 5.10.148, 5.15.73, 5.19.15 or 6.0.1 eliminates this vulnerability. Applying the patch d1ff475d7c83289d0a7faef346ea3bbf90818bad/c0aa76b0f17f59dd9c9d3463550a2986a1d592e4/ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48/70e4f70d54e0225f91814e8610477d65f33cefe4/1e555c3ed1fce4b278aaebe18a64a934cece57d8/64b79e632869ad3ef6c098a4731d559381da1115/81de80330fa6907aec32eb54c5619059e6e36452/2a96b532098284ecf8e4849b8b9e5fc7a28bdee9/2e488f13755ffbb60f307e991b27024716a33b29 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (265645) and CERT Bund (WID-SEC-2025-2087). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Amazon Linux 2
- Red Hat Enterprise Linux
- SUSE Linux
- Oracle Linux
- IBM QRadar SIEM
- Open Source Linux Kernel
- RESF Rocky Linux
- Dell Secure Connect Gateway
Product
Type
Vendor
Name
Version
- 4.9.330
- 4.14.295
- 4.19.261
- 5.4.217
- 5.10.147
- 5.15.0
- 5.15.1
- 5.15.2
- 5.15.3
- 5.15.4
- 5.15.5
- 5.15.6
- 5.15.7
- 5.15.8
- 5.15.9
- 5.15.10
- 5.15.11
- 5.15.12
- 5.15.13
- 5.15.14
- 5.15.15
- 5.15.16
- 5.15.17
- 5.15.18
- 5.15.19
- 5.15.20
- 5.15.21
- 5.15.22
- 5.15.23
- 5.15.24
- 5.15.25
- 5.15.26
- 5.15.27
- 5.15.28
- 5.15.29
- 5.15.30
- 5.15.31
- 5.15.32
- 5.15.33
- 5.15.34
- 5.15.35
- 5.15.36
- 5.15.37
- 5.15.38
- 5.15.39
- 5.15.40
- 5.15.41
- 5.15.42
- 5.15.43
- 5.15.44
- 5.15.45
- 5.15.46
- 5.15.47
- 5.15.48
- 5.15.49
- 5.15.50
- 5.15.51
- 5.15.52
- 5.15.53
- 5.15.54
- 5.15.55
- 5.15.56
- 5.15.57
- 5.15.58
- 5.15.59
- 5.15.60
- 5.15.61
- 5.15.62
- 5.15.63
- 5.15.64
- 5.15.65
- 5.15.66
- 5.15.67
- 5.15.68
- 5.15.69
- 5.15.70
- 5.15.71
- 5.15.72
- 5.19.0
- 5.19.1
- 5.19.2
- 5.19.3
- 5.19.4
- 5.19.5
- 5.19.6
- 5.19.7
- 5.19.8
- 5.19.9
- 5.19.10
- 5.19.11
- 5.19.12
- 5.19.13
- 5.19.14
- 6.0
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.9VulDB Meta Temp Score: 7.7
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 265645
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-50367
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.9.331/4.14.296/4.19.262/5.4.218/5.10.148/5.15.73/5.19.15/6.0.1
Patch: d1ff475d7c83289d0a7faef346ea3bbf90818bad/c0aa76b0f17f59dd9c9d3463550a2986a1d592e4/ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48/70e4f70d54e0225f91814e8610477d65f33cefe4/1e555c3ed1fce4b278aaebe18a64a934cece57d8/64b79e632869ad3ef6c098a4731d559381da1115/81de80330fa6907aec32eb54c5619059e6e36452/2a96b532098284ecf8e4849b8b9e5fc7a28bdee9/2e488f13755ffbb60f307e991b27024716a33b29
Timeline
09/17/2025 Advisory disclosed09/17/2025 CVE reserved
09/17/2025 VulDB entry created
12/27/2025 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-50367 (🔒)
GCVE (CVE): GCVE-0-2022-50367
GCVE (VulDB): GCVE-100-324690
CERT Bund: WID-SEC-2025-2087 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 09/17/2025 17:38Updated: 12/27/2025 02:41
Changes: 09/17/2025 17:38 (58), 09/21/2025 16:48 (2), 12/11/2025 00:38 (11), 12/27/2025 02:41 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.