LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26774: ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt

In the Linux kernel, the following vulnerability has been resolved: ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt Determine if bb_fragments is 0 instead of determining bb_free to eliminate the risk of dividing by zero when the block bitmap is corrupted.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-26774 is a Linux kernel ext4 filesystem flaw where corrupted block bitmap metadata can lead to a divide-by-zero condition. The public record does not provide CVSS severity or exploitation details. Business risk is mainly availability for Linux systems using affected kernels and ext4 filesystems.

Executive priority

Treat this as a kernel maintenance priority, not an emergency, unless affected ext4 systems support critical services. The absence of CVSS and exploitation evidence lowers urgency, but kernel availability issues deserve timely patching through normal change control.

Technical view

The fix changes ext4 mb_update_avg_fragment_size() to test bb_fragments for zero instead of bb_free, avoiding division by zero when ext4 block bitmap data is corrupt. The CVE record lists Linux kernel versions and stable commits, but downstream distribution impact depends on vendor backports.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with ext4 filesystems. The source bundle lists affected Linux kernel versions including 6.0, 6.1.80, 6.6.19, 6.7.7, and 6.8, but distribution-specific fixed package versions are not provided.

Exploitation context

No active exploitation is supported by the supplied sources, and the CVE is not listed as KEV. The record does not describe remote attackability or attacker prerequisites. Evidence only supports a kernel ext4 crash-risk condition triggered when corrupted block bitmap metadata is processed.

Researcher notes

The source data is limited to the CVE description and kernel stable references. It supports a divide-by-zero prevention fix in ext4, but not exploitability, privilege requirements, or impact beyond likely availability. Validate downstream exposure through distribution advisories, not upstream version numbers alone.

Mitigation direction

  • Apply Linux kernel updates from your distribution or kernel vendor.
  • Confirm updates include one of the referenced stable kernel fixes or equivalent backport.
  • Prioritize systems using ext4 for critical workloads or storage-heavy services.
  • Check vendor guidance before using filesystem repair as a mitigation.
  • Maintain tested backups for systems with important ext4 data.

Validation and detection

  • Inventory Linux kernel versions across hosts and appliances.
  • Identify systems with ext4 filesystems mounted or in use.
  • Compare installed kernels with vendor advisories and fixed package versions.
  • Confirm the ext4 fix is present through vendor changelogs or backport notes.
  • Review system logs for ext4 corruption warnings or kernel crash reports.
Prepared
Confidence
medium
Sources
7

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-26774 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
6Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux83e80a6e3543f37f74c8e48a5f305b054b65ce2a, 83e80a6e3543f37f74c8e48a5f305b054b65ce2a, 83e80a6e3543f37f74c8e48a5f305b054b65ce2a, 83e80a6e3543f37f74c8e48a5f305b054b65ce2a, 398a0fdb38d9ab5e68023667cc5e6e3d109e2d6b, 5.19.12unaffected
LinuxLinux6.0, 0, 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.