lwext4 through 1.0.0 Heap Buffer Overflow via ext4_fs_init_inode_bitmap
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| gkostka | lwext4 | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | lwext4 through 1.0.0 Heap Buffer Overflow via ext4_fs_init_inode_bitmap | |
| First Time appeared |
Gkostka
Gkostka lwext4 |
|
| Weaknesses | CWE-787 | |
| CPEs | cpe:2.3:a:gkostka:lwext4:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Gkostka
Gkostka lwext4 |
|
| References |
|
|
| Metrics |
cvssV3_1
|