Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-6684: FatFs GPT partition-scan loop DoS

Published Jul 1, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.6Medium · v3.1
EPSS0.31%24th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Elm-Chan
IdentifiersCVE-2026-6684CWE-835 · Loop with Unreachable Exit…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A successful exploit can cause the target device to hang or spend an effectively unbounded amount of time scanning partitions while mounting attacker-supplied media, resulting in denial of service and loss of availability. In embedded deployments this may present as boot-time hangs, stalled media initialization, or persistent service disruption until the malformed media is removed or the device is reset.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, disable or avoid GPT scanning where feasible, particularly configurations using FF_LBA64 = 1. Restrict exposure to untrusted removable media such as USB drives and SD cards, and avoid automatically mounting untrusted storage. Operational controls that limit physical access to media interfaces can reduce exploitability in embedded deployments.

Remediation

Patch, then assume compromise.

Upgrade FatFs to R0.16 or later, which upstream reportedly fixes this issue by addressing GPT validation relevant to the partition entry count. Downstream vendors using vendored or modified FatFs copies should verify that the R0.16 fix has been incorporated into their trees and rebuild/redeploy affected firmware accordingly.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Elm-ChanFatfsapplication
FAQ

Frequently asked questions

Is CVE-2026-6684 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-6684 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-6684?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-6684.
Is there a patch for CVE-2026-6684?
Upgrade FatFs to R0.16 or later, which upstream reportedly fixes this issue by addressing GPT validation relevant to the partition entry count. Downstream vendors using vendored or modified FatFs copies should verify that the R0.16 fix has been incorporated into their trees and rebuild/redeploy affected firmware accordingly.
What products are affected by CVE-2026-6684?
Elm-Chan Fatfs.
How severe is CVE-2026-6684?
CVE-2026-6684 has a CVSS v3.1 score of 4.6 (Medium) and an EPSS score of 0.31% (24th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.