Loading vulnerability…
CVE-2023-52622 is a Linux kernel ext4 flaw in online filesystem resizing when the filesystem was created with an excessively large flex block-group size. The resize path derives the size of its new-group metadata array from the flex group size and can request an allocation exceeding the kernel allocator's maximum order. This triggers an allocation warning and causes the online resize operation to fail. The fix limits each resize iteration to a bounded maximum number of block groups and performs multiple iterations as necessary, including when flex_bg metadata is dispersed.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel ext4 online-resize failure associated with oversized flex block groups.
A Linux kernel ext4 online filesystem-resize issue in which an oversized flex block-group configuration can cause an oversized allocation to fail. The reported failure is handled properly; the content questions whether this represents a security issue and characterizes the potential impact as low.
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.