CVE-2024-26772: ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
In the Linux kernel, the following vulnerability has been resolved:
ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
Places the logic for checking if the group's block bitmap is corrupt under
the protection of the group lock to avoid allocating blocks from the group
with a corrupted block bitmap.
Security readout for executives and security teams
Plain-English summary
A Linux ext4 filesystem race could allow block allocation from a group already identified as corrupted. This may further damage filesystem data or disrupt a system. The CVSS assessment requires local, low-privileged access; it is not described as remotely exploitable.
Executive priority
Treat as a high-priority kernel maintenance issue for affected ext4 hosts, especially shared systems with untrusted local users. Accelerate remediation where filesystem integrity or availability is business-critical. Internet-facing status alone does not determine exposure because the documented access vector is local.
Technical view
The vulnerability is a locking flaw in ext4_mb_find_by_goal(). The corrupted-block-bitmap check could occur without the group lock, permitting allocation from a corrupted group. The correction moves that check under the lock. CVSS 3.1 is 7.8, reflecting potential confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to Linux systems running an affected kernel and using ext4. The supplied version data names kernels from 3.12 through 6.8, but its exact range structure is ambiguous. Confirm applicability against the running distribution's advisory and kernel package.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and no user interaction. The supplied sources provide no evidence of public exploitation, and this CVE is not listed as KEV. The precise attacker-controlled trigger is not established by the bundle.
Researcher notes
The security boundary is the synchronization of the corrupted-group check with allocation decisions. Stable-kernel references show fixes across multiple branches. The bundle does not establish a reliable vulnerable commit range, practical exploitability, root escalation, or observed attacks; distribution-specific backport verification is therefore essential.
Mitigation direction
Install a distribution-supported kernel update containing the cited ext4 correction.
Follow vendor guidance to activate the corrected kernel, including reboot or approved live patching where applicable.
Prioritize ext4 systems accessible to untrusted or minimally privileged local users.
Check current Linux distribution advisories when package-to-upstream version mapping is unclear.
Validation and detection
Record each system's running kernel version and distribution package release.
Identify systems mounting ext4 filesystems and compare them with vendor advisories.
Verify the corrected kernel is active after remediation, not merely installed.
Review kernel and filesystem diagnostics for ext4 corruption or allocation-related errors.
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-2024-26772 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.
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.