littlefs denial of service via divide by zero in lfs_mount_()
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
The littlefs software has a divide-by-zero bug in lfs_mount_() that lets a local attacker crash any process that mounts a crafted filesystem image, causing a denial of service. The attack requires a user to mount the image but no login.
Written by a model
Original description
littlefs 2.8.0 through 2.11.3 contains a divide-by-zero vulnerability in lfs_mount_() that allows attackers to crash processes mounting crafted filesystem images when block_count is 0. Attackers can supply an image lacking a superblock entry or recording block_count 0, causing lfs->seed % lfs->block_count to trigger SIGFPE and denial of service.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2025-71472 (littlefs 2.8.0 through 2.11.3 Divide by Zero in lfs_mount_()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2025-71472 (entry last updated 2026-11-19):
Affected:
- littlefs-project littlefs: from 2.8.0, through 2.11.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2025-71472 is not listed as of cve.now's last read.
This KEV status is for CVE-2025-71472 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/littlefs-project/littlefs/pull/1226
- https://github.com/littlefs-project/littlefs/issues/1122
- https://github.com/littlefs-project/littlefs/blob/v2.11.3/lfs.c#L4640-L4645
- https://github.com/littlefs-project/littlefs
- https://www.vulncheck.com/advisories/littlefs-2.8.0-through-2.11.3-divide-by-zero-in-lfs-mount
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2025-71472
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2025-71472"}.Affected versions
- littlefs-project littlefsFrom 2.8.0 · through 2.11.3
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.8/10CVSS 6.8
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2025-71472 |
| Record | NVD · CVE-2025-71472 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · sigdevel/pocs · tree/main/res/littlefs/2 |
| Other links 5 | |
| Patch | GitHub · littlefs-project/littlefs · Pull request #1226 |
| Report | GitHub · littlefs-project/littlefs · Issue #1122 |
| Repository | GitHub · littlefs-project/littlefs · lfs.c · L4640-L4645 |
| Repository | GitHub · littlefs-project/littlefs · Repository |
| Link | vulncheck.com · advisories/littlefs-2.8.0-through-2.11.3-divide-by-zero-in-lfs-mount |
Questions about CVE-2025-71472
Is CVE-2025-71472 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2025-71472?
littlefs: from 2.8.0 through 2.11.3.
Source: cve.now feed data
Related
- CVE-2026-129490littlefs through 2.11.3 Type Confusion in lfs_dir_traverse via lfs_migrate
- CVE-2026-107359Malformed Wi-Fi Beacon Causes Crash on WF200
- CVE-2026-132762GPAC MP4Box before 26.07.0 Divide by Zero in DumpTrackInfo
- CVE-2026-125254FFmpeg through 9.0.2 Division by Zero via VVC ff_vvc_slice_rpl()
- CVE-2026-125232FFmpeg through 9.0.2 Division by Zero in B-frame Motion Estimation
- CVE-2026-125185FFmpeg through 9.0.2 Division by Zero via AFGS1 Film Grain Scaling Points
No corrections so far. Something wrong on this page? Report an error.