Type confusion in littlefs migration can crash processes
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- Passive
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-843 and the CVSS impact.
Summary
littlefs through 2.11.3, when built with LFS_MIGRATE, contains a type confusion flaw in lfs_dir_traverse() that treats a stack lfs_diskoff struct as an lfs_attr array (CWE-843). An attacker with local access who supplies a crafted littlefs v1 image during migration can cause out-of-bounds stack reads and crash the process. A public exploit is linked in the references.
Written with Claude Haiku 5.5 from the sources below · 2026-11-15
Description from the CNA
littlefs through 2.11.3, when built with LFS_MIGRATE, contains a type confusion vulnerability in lfs_dir_traverse() that treats a stack lfs_diskoff struct as an lfs_attr array. Attackers can supply a crafted littlefs v1 image whose metadata is read as LFS_FROM_USERATTRS during migration, causing out-of-bounds stack reads and process crashes.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| littlefs-project | littlefs | up to 2.11.3 | — | No fix listed | CNA |
- littlefs Vendorlittlefs-project Affected up to 2.11.3 Fixed in — No fix listed CNA
Remediation
The sources list no fixed version for littlefs.
Written with Claude Haiku 5.5 from the sources below · 2026-11-15
Timeline
- 2026-11-15 Threatist record created from CVE-2026-129490
- 2026-11-15 Alias added: GHSA-q985-5v39-r948
References
Sources
- CVE-2026-129490 · CVE Program
- CVE-2026-129490 · NVD
- FIRST EPSS
- GHSA-q985-5v39-r948 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences