FatFs versions prior to R0.16 contain a denial-of-service flaw in GPT partition scanning when GPT scanning is used with FF_LBA64 = 1. The loop count is derived from the GPT header field GPTH_PtNum without adequate bounds validation, allowing a malformed GPT header to force an extremely long or effectively unbounded scan during mount processing. The issue affects pre-R0.16 implementations that parse crafted GPT media and manifests as a loop with an unreachable or impractically distant exit condition during mount-time partition enumeration.
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.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity GPT partition scan loop flaw in pre-R0.16 FatFs versions that can cause unbounded scanning and boot-time denial of service.
A malformed GPT partition table handling flaw in FatFs that can cause devices to hang while mounting storage media.
A FatFs GPT parsing vulnerability in pre-R0.16 implementations caused by missing GPT entry-count validation, allowing unbounded partition-scan loops and mount-time denial-of-service.
A FatFs denial-of-service flaw where a malformed GPT partition table can hang a device during mount; this is the only one of the seven with an upstream fix in FatFs R0.16.
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.