CVE-2026-6683: Divide-by-zero in FatFs exFAT sync/write paths
- Vendor
- Elm-Chan
CVE-2026-6683 is a divide-by-zero vulnerability in FatFs R0.16 and earlier affecting exFAT sync and write logic. During write/sync operations on crafted exFAT media, attacker-controlled metadata can cause the expression n_fatent - 2 to evaluate to zero, triggering a divide-by-zero condition in the exFAT sync path. The issue is reachable when a vulnerable device processes malformed exFAT filesystem data, typically from removable media such as USB or SD storage, and in some deployments through firmware or OTA update pipelines that ingest filesystem images.
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.
Successful exploitation causes a reliable crash/denial-of-service condition in the affected device during exFAT write or sync handling. The primary impact is availability loss; the provided material does not indicate confidentiality or integrity impact from this flaw itself. In embedded update workflows, especially where exFAT-formatted update media is processed automatically, repeated or strategically timed crashes may interrupt firmware installation and can become a practical device-bricking vector.
Mitigation
If you can’t patch tonight, do this now.
Until patched code is deployed, reduce exposure by preventing untrusted exFAT media from being mounted or used in write/sync/update workflows. Restrict physical access to USB ports and SD slots, disable or gate exFAT support where not required, and harden firmware/OTA pipelines so update images and removable media are authenticated and validated before FatFs processes them. Avoid automatic processing of externally supplied update media where possible.
Remediation
Patch, then assume compromise.
Upgrade to a FatFs release newer than R0.16 that fixes the exFAT sync divide-by-zero issue. Because FatFs is commonly vendored into downstream SDKs and firmware trees, affected implementers should identify bundled copies in their products and apply or backport the vendor fix, then validate all exFAT write/sync and update-media handling paths.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
References
Frequently asked questions
- Is CVE-2026-6683 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-6683 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-6683?
- Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-6683.
- Is there a patch for CVE-2026-6683?
- Upgrade to a FatFs release newer than R0.16 that fixes the exFAT sync divide-by-zero issue. Because FatFs is commonly vendored into downstream SDKs and firmware trees, affected implementers should identify bundled copies in their products and apply or backport the vendor fix, then validate all exFAT write/sync and update-media handling paths.
- What products are affected by CVE-2026-6683?
- Elm-Chan Fatfs.
- How severe is CVE-2026-6683?
- CVE-2026-6683 has a CVSS v3.1 score of 4.6 (Medium) and an EPSS score of 0.31% (24th percentile) as of Sep 25, 2026.
Recent activity
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.