CVE-2025-68251 is a Linux kernel vulnerability in EROFS compressed data metadata handling. According to the provided fix description, corrupted subpage compact indexes can encode an invalid clusterofs value larger than lclustersize for non-head logical clusters, which can cause the kernel to enter an infinite loop while processing a crafted EROFS image. The issue was addressed by moving the bounds check used for full compression indexes into z_erofs_load_lcluster_from_disk() so that it also validates subpage compact compression indexes, and by correcting the placement of the m->type >= Z_EROFS_LCLUSTER_TYPE_MAX validation after z_erofs_load_{compact,full}_lcluster() parsing.
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.
linux package on Debian stable (trixie) to version 6.12.94-1 or a later fixed version supplied by Debian. More generally, deploy a Linux kernel release that includes the EROFS fix adding validation for corrupted subpage compact indexes in z_erofs_load_lcluster_from_disk().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.
6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.