Loading vulnerability…
CVE-2025-38172 is a use-after-free in the Linux kernel EROFS filesystem mount path for multi-device filesystems. A configuration with a block-device primary EROFS device and a file-backed extra device causes erofs_init_device() to return -ENOTBLK. erofs_fc_get_tree() did not treat that result as fatal, allowing the mount path to deactivate the superblock and free the EROFS superblock-private structure before subsequently accessing it to open the extra file-backed device. The fix rejects this invalid mixed-device configuration by converting the condition to -EINVAL.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel EROFS use-after-free vulnerability caused by a device type mismatch.
A Linux kernel EROFS filesystem use-after-free vulnerability caused by improper handling of a mixed block-device and file-backed-device configuration.
A Linux kernel EROFS use-after-free vulnerability caused by a device type mismatch.
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.