lwext4 through 1.0.0 contains an out-of-bounds write vulnerability in ext4fsinitblockbitmap() that allows attackers to corrupt heap memory via crafted superblock geometry fields. Attackers can supply an ext4 image with oversized sreservedgdtblocks and BLOCKUNINIT groups to write past the bitmap buffer, crashing applications that mount it.
An out-of-bounds read in the ext4extbinsearchidx function in src/ext4extent.c of the lwext4 1.0.0 library allows attackers to cause a denial of service by supplying a specially crafted ext4 filesystem image. The vulnerability occurs due to insufficient validation of extent header fields before performing a binary search over extent index entries, which can result in invalid pointer calculations and an out-of-bounds memory read during extent tree traversal.
A NULL pointer dereference in the ext4direngetnamelen function in include/ext4dir.h of lwext4 1.0.0 allows attackers to cause a denial of service by supplying a specially crafted EXT4 filesystem image with malformed directory entries. During directory iteration, the code may fail to validate the directory entry pointer before accessing the namelen field, resulting in a segmentation fault. This affects versions based on (or equivalent to) the 2016-era codebase (1.0.0).
Product: lwext4 Affected: lwext4 1.0.0, commit 58bcf89a121b72d4fb66334f1693d3b30e4cb9c5 CVE: CVE-2025-70099 CWE: CWE-476 (NULL Pointer Dereference) CVSS 3.1: 7.5 HIGH (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Reporter: Alexander A. Shvedov (@sigdevel) & Daniil Dulov
Description: A NULL pointer dereference exists in lwext4 when processing a crafted EXT4 filesystem image containing malformed directory entries.
During directory iteration, ext4direntrynext() may call the inline helper ext4direngetnamelen() with a NULL or otherwise invalid directory entry pointer. ext4direngetnamelen() then reads the namelen field without validating the pointer first:
include/ext4dir.h:126 Function: ext4direngetnamelen()
src/ext4.c:3233 Function: ext4direntrynext()
This results in a segmentation fault while reading from address 0x6. An attacker who can supply a crafted or corrupted EXT4 image to an application using lwext4 for parsing or directory traversal can cause an abnormal process termination. No evidence of code execution was observed.
Reproduction: The issue is reproducible with the public PoC image using the fuzzing harness:
./aflext4mountread ./sig1121lwext4ext4dirh126
ASan log excerpt: AddressSanitizer:DEADLYSIGNAL ==1900815==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000006 ==1900815==The signal is caused by a READ memory access. #0 0x561280525f64 in ext4direngetnamelen /home/labuser/target/2025/lwext4/include/ext4dir.h:126:19 #1 0x561280525f64 in ext4direntrynext /home/labuser/target/2025/lwext4/src/ext4.c:3233:16 #2 0x561280518d54 in LLVMFuzzerTestOneInput /home/labuser/target/2025/fuzz/ext4mountread/fuzzext4mountread.c:29:30 SUMMARY: AddressSanitizer: SEGV /home/labuser/target/2025/lwext4/include/ext4dir.h:126:19 in ext4direngetnamelen
Fix: The issue is addressed in lwext4 v1.0.1, released by Aladdin-R-D. Users should upgrade to v1.0.1 or apply the corresponding upstream patch.
References: https://github.com/gkostka/lwext4/issues/89 https://github.com/sigdevel/pocs/blob/main/res/lwext4/1/sig1121lwext4ext4dirh126 https://github.com/Aladdin-R-D/lwext4/releases/tag/v1.0.1 https://www.cve.org/CVERecord?id=CVE-2025-70099 https://nvd.nist.gov/vuln/detail/CVE-2025-70099 https://infosec.exchange/@sigdevel/116668939725424227 https://bdu.fstec.ru/vul/2025-15477
—— Best regards, Alexander A. Shvedov @sigdevel