Answer in brief
CVE-2026-31449 records a High severity (CVSS 7.8) vulnerability in ext4: validate p_idx bounds in ext4_ext_correct_indexes. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-31449 records a High severity (CVSS 7.8) vulnerability in ext4: validate p_idx bounds in ext4_ext_correct_indexes. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <39d6e2b67651614bac0dc6592fa9836321910067 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <c5839b34704c9c2f47f079451bdbb22de0da1ed1 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <10242e640b36b91ad03d25f3dc77854bbdff8358 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <4d08401aa13f1531216f1a7ae281ca4806e90a5c || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <407c944f217c17d4343148011acafebc604d55e1 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <93f2e975ed658ce09db4d4c2877ca2c06540df83 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <01bf1e0b997d82c0e353b51ed74ef99698043c33 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8 | 39d6e2b67651614bac0dc6592fa9836321910067, c5839b34704c9c2f47f079451bdbb22de0da1ed1, 10242e640b36b91ad03d25f3dc77854bbdff8358, 4d08401aa13f1531216f1a7ae281ca4806e90a5c, 407c944f217c17d4343148011acafebc604d55e1, 93f2e975ed658ce09db4d4c2877ca2c06540df83, 01bf1e0b997d82c0e353b51ed74ef99698043c33, 2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8 |
| Linux/Linuxgeneric | 2.6.19 | Not reported |
Published upstream
Apr 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <39d6e2b67651614bac0dc6592fa9836321910067 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <c5839b34704c9c2f47f079451bdbb22de0da1ed1 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <10242e640b36b91ad03d25f3dc77854bbdff8358 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <4d08401aa13f1531216f1a7ae281ca4806e90a5c || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <407c944f217c17d4343148011acafebc604d55e1 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <93f2e975ed658ce09db4d4c2877ca2c06540df83 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <01bf1e0b997d82c0e353b51ed74ef99698043c33 || >=a86c61812637c7dd0c57e29880cffd477b62f2e7 <2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8 | 39d6e2b67651614bac0dc6592fa9836321910067, c5839b34704c9c2f47f079451bdbb22de0da1ed1, 10242e640b36b91ad03d25f3dc77854bbdff8358, 4d08401aa13f1531216f1a7ae281ca4806e90a5c, 407c944f217c17d4343148011acafebc604d55e1, 93f2e975ed658ce09db4d4c2877ca2c06540df83, 01bf1e0b997d82c0e353b51ed74ef99698043c33, 2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8 |
| Linux/Linuxgeneric | 2.6.19 | Not reported |
Published upstream
Apr 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.