CVE-2022-50367 is an improper-initialization flaw in the Linux kernel NILFS filesystem metadata-inode destruction path. During inode allocation, inode_init_always() can fail with an out-of-memory error when security_inode_alloc() fails, leaving inode->i_private uninitialized. NILFS metadata-file detection can subsequently classify the inode as a metadata inode, causing nilfs_free_inode() to invoke nilfs_mdt_destroy(). That routine frees the uninitialized private pointer, resulting in a use-after-free condition or general protection fault. The upstream correction reorders security_inode_alloc() to occur immediately before incrementing the inode count, preventing the erroneous cleanup path.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free/general-protection-fault flaw in the Linux kernel NILFS filesystem teardown path.
A Linux kernel NILFS filesystem use-after-free/general-protection-fault issue in nilfs_mdt_destroy.
Linux kernel NILFS filesystem use-after-free/general-protection-fault bug in nilfs_mdt_destroy.
Linux kernel NILFS filesystem use-after-free/general-protection-fault bug in nilfs_mdt_destroy.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.