CVE-2022-50673 is a use-after-free vulnerability in the Linux kernel ext4 filesystem's orphan-inode cleanup path during filesystem mount. When ext4 orphan cleanup processes an orphaned inode, it adds the inode to the orphan list and may invoke truncation. If journal-inode attachment then fails with an out-of-memory error, the inode can be released while the last-orphan state still references it. A subsequent cleanup iteration can add the already freed inode to the orphan list, dereferencing freed memory. The upstream fix propagates the journal-inode attachment failure correctly, preventing reuse of the stale inode reference.
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.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel ext4 use-after-free vulnerability in ext4_orphan_cleanup.
A Linux kernel ext4 use-after-free vulnerability in ext4_orphan_cleanup.
A Linux kernel ext4 use-after-free vulnerability in ext4_orphan_cleanup.
A Linux kernel ext4 use-after-free vulnerability in ext4_orphan_cleanup.
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.