CVE-2026-6684 json
FatFs Infinite Loop in GPT Partition Scan
published 2026-07-01 4 mo ago modified 2026-10-25 14 d ago also EUVD-2026-40994
- cvss
- 4.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
FatFs prior to R0.16 that use GPT scanning with 'FF_LBA64 = 1' contains an issue where an unbounded loop count derived from GPT header field GPTH_PtNum, enabling extremely long or effectively infinite mount-time scans. This maps to CWE-835 (Loop with Unreachable Exit Condition). Estimated CVSS v3.1 vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (4.6, Medium). The estimated CISA SSVC vectors are Exploitation: PoC, Technical Impact: Partial.
Patch / fix
- ChaN FatFs R0.16
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/runZeroInc/vulns-2026-fatfs-chance referenced PoC, tagged "exploit" by a source, unverified
- runzero.com https://www.runzero.com/blog/fatfs-bugs/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.6 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- ChaN FatFs
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
github.com
/runZeroInc/vulns-2026-fatfs-chance
technical-description, exploit, third-party-advisory
-
runzero.com
/blog/fatfs-bugs/
third-party-advisory, exploit
-
elm-chan.org
/fsw/ff/
product
-
runzero.com
/advisories/fatfs-gpt-scan-loop-dos-cve-2026-6684/
third-party-advisory
Sources
- CVE List CVE-2026-6684
- NVD CVE-2026-6684
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.