ext4: validate p_idx bounds in ext4_ext_correct_indexes
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.259, 5.15.210, 6.1.175, 6.6.140, 6.12.80, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From a86c61812637c7dd0c57e29880cffd477b62f2e7 · fixed in 39d6e2b67651614bac0dc6592fa9836321910067; From a86c61812637c7dd0c57e29880cffd477b62f2e7 · fixed in c5839b34704c9c2f47f079451bdbb22de0da1ed1; From a86c61812637c7dd0c57e29880cffd477b62f2e7 · fixed in 10242e640b36b91ad03d25f3dc77854bbdff8358; From a86c61812637c7dd0c57e29880cffd477b62f2e7 · fixed in 4d08401aa13f1531216f1a7ae281ca4806e90a5c; From a86c61812637c7dd0c57e29880cffd477b62f2e7 · fixed in 407c944f217c17d4343148011acafebc604d55e1; From a86c61812637c7dd0c57e29880cffd477b62f2e7 · fixed in 93f2e975ed658ce09db4d4c2877ca2c06540df83; From a86c61812637c7dd0c57e29880cffd477b62f2e7 · fixed in 01bf1e0b997d82c0e353b51ed74ef99698043c33; From a86c61812637c7dd0c57e29880cffd477b62f2e7 · fixed in 2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8
- Linux Linux
2.6.19
- KernelLinux
From 2.6.19 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.175; From 6.2.0 · fixed in 6.6.140; From 6.7.0 · fixed in 6.12.80; From 6.13.0 · fixed in 6.18.21; From 6.19.0 · fixed in 6.19.11
References 8
git.kernel.org
- stable/c/39d6e2b67651614bac0dc6592fa9836321910067
- stable/c/c5839b34704c9c2f47f079451bdbb22de0da1ed1
- stable/c/10242e640b36b91ad03d25f3dc77854bbdff8358
- stable/c/4d08401aa13f1531216f1a7ae281ca4806e90a5c
- stable/c/407c944f217c17d4343148011acafebc604d55e1
- stable/c/93f2e975ed658ce09db4d4c2877ca2c06540df83
- stable/c/01bf1e0b997d82c0e353b51ed74ef99698043c33
- stable/c/2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8