lwext4 out-of-bounds write in block bitmap initialization
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
lwext4 is affected by an out-of-bounds write in its block bitmap initialization routine. An attacker who gets a user to open a crafted ext4 image can corrupt heap memory, which can crash any application that mounts it.
Written by a model
Original description
lwext4 through 1.0.0 contains an out-of-bounds write vulnerability in ext4_fs_init_block_bitmap() that allows attackers to corrupt heap memory via crafted superblock geometry fields. Attackers can supply an ext4 image with oversized s_reserved_gdt_blocks and BLOCK_UNINIT groups to write past the bitmap buffer, crashing applications that mount it.
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-71474 (lwext4 through 1.0.0 Out-of-Bounds Write via ext4_fs_init_block_bitmap), 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-71474 (entry last updated 2026-11-20):
Affected:
- gkostka lwext4: through 1.0.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2025-71474 is not listed as of cve.now's last read.
This KEV status is for CVE-2025-71474 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/gkostka/lwext4/pull/111
- https://github.com/gkostka/lwext4/commit/b9c842f168e6044bd03fe34e1237eda33c299908
- https://github.com/Aladdin-R-D/lwext4/commit/2f5714d42f729fbdf3e65fd24d57149619fa1f33
- https://github.com/gkostka/lwext4/issues/92
- https://github.com/gkostka/lwext4/blob/v1.0.0/src/ext4_fs.c#L322-L334
- https://github.com/gkostka/lwext4/blob/v1.0.0/include/ext4_bitmap.h#L53-L56
- https://github.com/gkostka/lwext4
- https://www.vulncheck.com/advisories/lwext4-through-1.0.0-out-of-bounds-write-via-ext4-fs-init-block-bitmap
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-71474
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-71474"}.Affected versions
- gkostka lwext4through 1.0.0
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- 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 44 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 10
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2025-71474 |
| Record | NVD · CVE-2025-71474 |
| Other links 8 | |
| Patch | GitHub · gkostka/lwext4 · Pull request #111 |
| Patch | GitHub · gkostka/lwext4 · Commit b9c842f1 |
| Patch | GitHub · Aladdin-R-D/lwext4 · Commit 2f5714d4 |
| Report | GitHub · gkostka/lwext4 · Issue #92 |
| Repository | GitHub · gkostka/lwext4 · src/ext4_fs.c · L322-L334 |
| Repository | GitHub · gkostka/lwext4 · include/ext4_bitmap.h · L53-L56 |
| Repository | GitHub · gkostka/lwext4 · Repository |
| Link | vulncheck.com · advisories/lwext4-through-1.0.0-out-of-bounds-write-via-ext4-fs-init-block-bitmap |
Questions about CVE-2025-71474
Is CVE-2025-71474 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2025-71474?
lwext4: through 1.0.0.
Source: cve.now feed data
Related
- CVE-2025-71473lwext4 through 1.0.0 Heap Buffer Overflow via ext4_fs_init_inode_bitmap
- CVE-2026-133528BeamNG.drive before 0.40.6 LuaJIT FFI Sandbox Escape via JIT Bounds-Check Bypass
- CVE-2026-77347Pozeiden: Out-of-bounds read/write (crash / memory corruption) on valid diagrams in grid-layout renderers
- CVE-2026-62258HTSlib: Stack write overflow in HTSlib CRAM decoder
- CVE-2026-62257HTSlib: Heap read and write overflow in HTSlib CRAM 4.0 decoder
- CVE-2026-63390HTSlib: Heap buffer overflow in BCF reader due to improper validation of input.
No corrections so far. Something wrong on this page? Report an error.