CVE-2025-22113 is a race condition in the Linux kernel ext4 filesystem during unmount and error handling. An ext4 inode error can schedule deferred superblock-update work while JBD2 journal destruction is in progress. The deferred worker can subsequently attempt to start a journal transaction after the journal has been marked with JBD2_UNMOUNT, triggering a BUG_ON. The fix introduces an ext4 mount state indicating that journal destruction is underway, prevents deferred journaled superblock updates in that state, and performs the required superblock update outside the journal.
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.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel ext4 filesystem flaw involving a superblock journaling update during an error condition while the journal is being destroyed.
A Linux kernel ext4 filesystem flaw involving a superblock journal update when an error occurs while the journal is being destroyed.
Linux kernel ext4 error-path flaw during journal destruction.
Linux kernel ext4 filesystem vulnerability involving superblock journaling during journal destruction after an error.
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.