cve.bz

CVE-2025-71473 lwext4 through 1.0.0 Heap Buffer Overflow via ext4_fs_init_inode_bitmap

6.9 mediumEPSS 0.1%

Medium (6.9) in gkostka lwext4. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
lwext4 through 1.0.0 contains a heap buffer overflow in ext4_fs_init_inode_bitmap() in src/ext4_fs.c because it does not validate s_inodes_per_group against the inode bitmap size. Attackers can supply a crafted ext4 image with an oversized s_inodes_per_group so memset writes past the heap buffer, corrupting memory and crashing the mounting application.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

6.1 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-787 Out-of-bounds Write
Published
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-71473 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-71473?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-71473?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-71473 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
gkostka lwext4through 1.0.0

References

Check your stackJSON