Linux vulnerability

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.

Published 22 Apr 2026Updated 8 Sep 20269 sources
CVSS 7.8

What happened

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.

Affected versions

Linux: a86c61812637c7dd0c57e29880cffd477b62f2e7 through before 39d6e2b67651614bac0dc6592fa9836321910067 (git); a86c61812637c7dd0c57e29880cffd477b62f2e7 through before c5839b34704c9c2f47f079451bdbb22de0da1ed1 (git); a86c61812637c7dd0c57e29880cffd477b62f2e7 through before 10242e640b36b91ad03d25f3dc77854bbdff8358 (git); a86c61812637c7dd0c57e29880cffd477b62f2e7 through before 4d08401aa13f1531216f1a7ae281ca4806e90a5c (git); a86c61812637c7dd0c57e29880cffd477b62f2e7 through before 407c944f217c17d4343148011acafebc604d55e1 (git); a86c61812637c7dd0c57e29880cffd477b62f2e7 through before 93f2e975ed658ce09db4d4c2877ca2c06540df83 (git); a86c61812637c7dd0c57e29880cffd477b62f2e7 through before 01bf1e0b997d82c0e353b51ed74ef99698043c33 (git); a86c61812637c7dd0c57e29880cffd477b62f2e7 through before 2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8 (git); 2.6.19; V3.1.6 through before * (custom) Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.