CVE-2022-50367
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-17

Last updated on: 2025-12-10

Assigner: kernel.org

Description
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)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-17
Last Modified
2025-12-10
Generated
2026-05-07
AI Q&A
2025-09-17
EPSS Evaluated
2026-05-05
NVD
CVE-2022-50367
Affected Vendors & Products
Showing 8 associated CPEs
Vendor Product Version / Range
linux linux_kernel to 4.9.331 (exc)
linux linux_kernel From 4.10 (inc) to 4.14.296 (exc)
linux linux_kernel From 4.15 (inc) to 4.19.262 (exc)
linux linux_kernel From 4.20 (inc) to 5.4.218 (exc)
linux linux_kernel From 5.5 (inc) to 5.10.148 (exc)
linux linux_kernel From 5.11 (inc) to 5.15.73 (exc)
linux linux_kernel From 5.16 (inc) to 5.19.15 (exc)
linux linux_kernel From 6.0 (inc) to 6.0.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a use-after-free (UAF) and general protection fault (GPF) bug in the Linux kernel related to the nilfs_mdt_destroy function. It occurs because inode_init_always() can return an error (-ENOMEM) if security_inode_alloc() fails, leaving inode->i_private uninitialized. Subsequently, nilfs_is_metadata_file_inode() incorrectly returns true, causing nilfs_free_inode() to call nilfs_mdt_destroy() on an uninitialized inode->i_private, which leads to freeing invalid memory and results in crashes.


How can this vulnerability impact me? :

This vulnerability can cause system crashes due to use-after-free or general protection faults in the Linux kernel. Such crashes can lead to denial of service or instability in systems running affected kernel versions.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart