ext4: validate p_idx bounds in ext4_ext_correct_indexes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a86c61812637c7dd0c57e29880cffd477b62f2e7 · < 93f2e975ed658ce09db4d4c2877ca2c06540df83| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: validate p_idx bounds in ext4_ext_correct_indexes
ext4_ext_correct_indexes() walks up the extent tree correcting index entries when the first extent in a leaf is modified. Before accessing path[k].p_idx->ei_block, there is no validation that p_idx falls within the valid range of index entries for that level.
If the on-disk extent header contains a corrupted or crafted eh_entries value, p_idx can point past the end of the allocated buffer, causing a slab-out-of-bounds read.
Fix this by validating path[k].p_idx against EXT_LAST_INDEX() at both access sites: before the while loop and inside it. Return -EFSCORRUPTED if the index pointer is out of range, consistent with how other bounds violations are handled in the ext4 extent tree code.
From the CVE record · Linux
The Linux kernel’s ext4 extent-index correction code does not validate an index pointer before reading it. A corrupted or crafted on-disk extent header can cause a slab-out-of-bounds read when the kernel processes it. The input does not specify whether authentication or user interaction is required.
Engineers running Linux kernels with ext4 support should check their kernel versions; affected versions are not specified in the input.