LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26601: ext4: regenerate buddy after block freeing failed if under fc replay

In the Linux kernel, the following vulnerability has been resolved: ext4: regenerate buddy after block freeing failed if under fc replay This mostly reverts commit 6bd97bf273bd ("ext4: remove redundant mb_regenerate_buddy()") and reintroduces mb_regenerate_buddy(). Based on code in mb_free_blocks(), fast commit replay can end up marking as free blocks that are already marked as such. This causes corruption of the buddy bitmap so we need to regenerate it in that case.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel ext4 filesystem bug. During fast commit replay, the kernel can incorrectly free blocks already marked free, corrupting ext4 allocation metadata. The main business risk is filesystem integrity and host availability, especially after crash recovery or journal replay on affected kernels.

Executive priority

Treat this as a kernel maintenance and data-integrity issue. Prioritize patching critical Linux systems using ext4, but do not escalate as internet-wide emergency based on the provided evidence.

Technical view

The fix reintroduces ext4 mb_regenerate_buddy() handling after block-free failure during fast commit replay. Without regeneration, ext4 buddy bitmap state can become inconsistent when replay marks already-free blocks as free. The sources identify Linux kernel stable fixes across affected branches, but provide no CVSS, CWE, or exploit details.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions with ext4 filesystems where fast commit replay can occur. The bundle does not identify remote attack surface, application-level exposure, or affected non-Linux products.

Exploitation context

No active exploitation is supported by the provided sources. The CVE is not listed as KEV in the bundle, and the references describe a kernel correctness fix rather than public exploitation.

Researcher notes

The source evidence supports a fast commit replay metadata corruption bug in ext4. Missing data includes CVSS, precise distro package boundaries beyond referenced advisories, exploitability analysis, and attacker prerequisites. Avoid assuming remote exploitability or active abuse.

Mitigation direction

  • Apply vendor kernel updates that include the referenced upstream stable fixes.
  • Prioritize hosts using ext4 for critical workloads or persistent data.
  • Review Debian LTS or distribution advisories for fixed package versions.
  • Maintain current backups before kernel updates on storage-critical systems.

Validation and detection

  • Inventory Linux kernel versions against vendor fixed releases.
  • Identify systems using ext4 on production or critical data volumes.
  • Confirm patched kernels include the referenced stable ext4 fix commits.
  • Review filesystem logs after crashes or reboots for ext4 errors.
Prepared
Confidence
medium
Sources
9

Public sources used

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-26601 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
8Source links

SSVC decision data

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

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
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0983142c5f17a62055ec851372273c3bc77e4788, 6bd97bf273bdb4944904e57480f6545bca48ad77, 6bd97bf273bdb4944904e57480f6545bca48ad77, 6bd97bf273bdb4944904e57480f6545bca48ad77, 6bd97bf273bdb4944904e57480f6545bca48ad77, 6bd97bf273bdb4944904e57480f6545bca48ad77, 5.10.181unaffected
LinuxLinux5.11, 0, 5.10.211, 5.15.150, 6.1.78, 6.6.17, 6.7.5, 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.