CVE-2026-6688: CWE-120 Buffer Copy without Checking Size of Input in ChaN FatFs
FatFs R0.16 and earlier contains a downstream-caller vulnerability pattern associated with FatFs long filename handling. With LFN enabled, fno.fname can be up to 255 characters; many callers copy it into short fixed buffers without bounds checks, causing overflow. This maps to CWE-120 (Buffer Copy without Checking Size of Input). Estimated CVSS v3.1 vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (7.6, High). The estimated CISA SSVC vectors are Exploitation: PoC, Technical Impact: Total.
AI Analysis
Technical Summary
The vulnerability in ChaN FatFs R0.16 and earlier arises from improper handling of long filenames. Specifically, with LFN enabled, the fno.fname field can hold filenames up to 255 characters, but many functions downstream copy this data into smaller fixed buffers without verifying the size, causing buffer overflow conditions. This is a classic instance of CWE-120. The CVSS v3.1 base score is 7.6 (High), with attack vector being physical (AV:P), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), scope changed (S:C), and high impact on confidentiality, integrity, and availability (C:H/I:H/A:H). The CISA SSVC assessment indicates proof-of-concept exploitation exists and the technical impact is total compromise.
Potential Impact
Successful exploitation can lead to total compromise of the affected system, including full confidentiality, integrity, and availability loss. The buffer overflow can allow attackers to execute arbitrary code or cause denial of service. The vulnerability requires physical access to the device (AV:P) but no privileges or user interaction, making it a significant risk in environments where physical access is possible.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround has been documented at this time. Users should monitor for vendor updates and apply patches once available. Until then, limiting physical access to affected devices may reduce risk.
CVE-2026-6688: CWE-120 Buffer Copy without Checking Size of Input in ChaN FatFs
Description
FatFs R0.16 and earlier contains a downstream-caller vulnerability pattern associated with FatFs long filename handling. With LFN enabled, fno.fname can be up to 255 characters; many callers copy it into short fixed buffers without bounds checks, causing overflow. This maps to CWE-120 (Buffer Copy without Checking Size of Input). Estimated CVSS v3.1 vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (7.6, High). The estimated CISA SSVC vectors are Exploitation: PoC, Technical Impact: Total.
CVSS v3.1
Score 7.6high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in ChaN FatFs R0.16 and earlier arises from improper handling of long filenames. Specifically, with LFN enabled, the fno.fname field can hold filenames up to 255 characters, but many functions downstream copy this data into smaller fixed buffers without verifying the size, causing buffer overflow conditions. This is a classic instance of CWE-120. The CVSS v3.1 base score is 7.6 (High), with attack vector being physical (AV:P), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), scope changed (S:C), and high impact on confidentiality, integrity, and availability (C:H/I:H/A:H). The CISA SSVC assessment indicates proof-of-concept exploitation exists and the technical impact is total compromise.
Potential Impact
Successful exploitation can lead to total compromise of the affected system, including full confidentiality, integrity, and availability loss. The buffer overflow can allow attackers to execute arbitrary code or cause denial of service. The vulnerability requires physical access to the device (AV:P) but no privileges or user interaction, making it a significant risk in environments where physical access is possible.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround has been documented at this time. Users should monitor for vendor updates and apply patches once available. Until then, limiting physical access to affected devices may reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- runZero
- Date Reserved
- 2026-04-20T15:06:24.308Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a45260e27e9c79719982d2e
Added to database: 07/01/2026, 14:37:02 UTC
Last enriched: 07/01/2026, 14:51:17 UTC
Last updated: 07/01/2026, 15:36:53 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.