LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
6

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-26772Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux163a203ddb36c36d4a1c942aececda0cc8d06aa7, 163a203ddb36c36d4a1c942aececda0cc8d06aa7, 163a203ddb36c36d4a1c942aececda0cc8d06aa7, 163a203ddb36c36d4a1c942aececda0cc8d06aa7, 163a203ddb36c36d4a1c942aececda0cc8d06aa7, 163a203ddb36c36d4a1c942aececda0cc8d06aa7, 163a203ddb36c36d4a1c942aececda0cc8d06aa7, 163a203ddb36c36d4a1c942aececda0cc8d06aa7unaffected
LinuxLinux3.12, 0, 4.19.308, 5.4.270, 5.10.211, 5.15.150, 6.1.80, 6.6.19, 6.7.7, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.