Loading vulnerability…
FatFs R0.16 and earlier contains an information disclosure flaw in file-extension handling. When f_lseek() is used to extend a file beyond its current end-of-file, newly allocated clusters are not zero-filled before becoming part of the file. As a result, subsequent reads from the extended region can expose residual data previously stored in those clusters, including stale content from deleted files. The issue is described as an uninitialized cluster exposure path in FatFs and affects implementations that rely on the library’s file growth behavior without explicitly clearing newly allocated storage.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A FatFs information disclosure issue where extending a file past its end can expose residual data from previously deleted files.
An information disclosure vulnerability in FatFs where extending files beyond EOF can expose uninitialized clusters and leak stale data from previously deleted content.
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.