CVE-2026-31449: ext4: validate p_idx bounds in ext4_ext_correct_indexes
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.
Security readout for executives and security teams
Plain-English summary
A malformed or corrupted ext4 filesystem can make the Linux kernel read beyond an allocated memory buffer while updating filesystem indexes. Exploitation requires local interaction with affected filesystem data, so this is not described as a directly remote flaw. Successful triggering could expose sensitive memory, corrupt system behavior, or crash a host.
Executive priority
Prioritize patching systems that ingest untrusted storage, virtual-disk images, backups, or removable media. Treat ordinary servers with only trusted local ext4 storage as lower immediate exposure, while still updating through normal kernel maintenance. Escalate rapidly if monitoring identifies ext4 corruption or kernel memory-safety reports.
Technical view
ext4_ext_correct_indexes() trusted an extent-header entry count when deriving p_idx. Crafted or corrupted eh_entries metadata could place p_idx beyond EXT_LAST_INDEX(), causing a slab out-of-bounds read at two ei_block access sites. The stable fixes validate both accesses and return -EFSCORRUPTED when the pointer exceeds valid index bounds.
Likely exposure
Exposure is most plausible on affected Linux systems that mount or process untrusted, removable, imported, or attacker-influenced ext4 filesystems or images. The supplied version data is ambiguously structured, so administrators should map their distribution kernel package to vendor advisories or the referenced stable commits rather than relying solely on version numbers.
Exploitation context
The supplied CVSS vector is local, low-complexity, requires no privileges, and requires user interaction. The bundle does not report CISA KEV inclusion or provide evidence of active exploitation. A crafted or corrupted ext4 extent tree is required; direct network exploitation is not established by the supplied sources.
Researcher notes
No CWE is supplied. The documented primitive is a slab out-of-bounds read caused by insufficient p_idx validation. Although CVSS claims high confidentiality, integrity, and availability impacts, the bundle does not establish a demonstrated exploit outcome. Exact affected and fixed package boundaries require distribution-specific confirmation.
Mitigation direction
Install a vendor-supported kernel containing the applicable referenced stable fix.
Check distribution guidance to map packaged kernels and backports to the fix.
Restrict mounting or processing of untrusted ext4 media and filesystem images until updated.
Apply least privilege to workflows handling removable, imported, or externally supplied storage.
Validation and detection
Inventory Linux kernel packages on systems that handle ext4 filesystems or images.
Confirm the installed kernel includes the applicable stable fix or vendor backport.
Review storage workflows for attacker-influenced ext4 media, images, snapshots, or virtual disks.
Check kernel and filesystem logs for ext4 corruption or slab out-of-bounds reports.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31449 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.