LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31451: ext4: replace BUG_ON with proper error handling in ext4_read_inline_folio

In the Linux kernel, the following vulnerability has been resolved: ext4: replace BUG_ON with proper error handling in ext4_read_inline_folio Replace BUG_ON() with proper error handling when inline data size exceeds PAGE_SIZE. This prevents kernel panic and allows the system to continue running while properly reporting the filesystem corruption. The error is logged via ext4_error_inode(), the buffer head is released to prevent memory leak, and -EFSCORRUPTED is returned to indicate filesystem corruption.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel ext4 issue can turn certain filesystem corruption into a kernel panic. In business terms, affected systems may crash instead of safely reporting the damaged filesystem condition. The source bundle does not show data theft, privilege escalation, CVSS scoring, or active exploitation.

Executive priority

Treat this as a reliability and service-availability fix, not a confirmed breach-risk emergency. Patch through normal kernel maintenance, accelerating for critical ext4-backed systems or environments that handle untrusted filesystem media.

Technical view

The fix replaces a BUG_ON() in ext4_read_inline_folio with error handling when inline data size exceeds PAGE_SIZE. The patched path logs via ext4_error_inode(), releases the buffer head, and returns -EFSCORRUPTED instead of panicking the kernel.

Likely exposure

Exposure is most relevant to Linux systems using ext4, especially where corrupted or untrusted ext4 filesystems, disk images, removable media, or storage snapshots may be mounted. The bundle lists Linux kernel versions and stable commits but does not provide distribution-specific package status.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The described impact is availability: a kernel panic from a filesystem corruption condition. The sources do not establish remote exploitability or a weaponized exploit.

Researcher notes

Evidence is limited to the CVE text and kernel stable references. The key behavior change is panic-to-error handling for oversized inline data. Affected-version detail is incomplete for downstream distributions, so validation should rely on vendor kernel advisories and commit inclusion.

Mitigation direction

  • Apply vendor Linux kernel updates that include the referenced stable ext4 fixes.
  • Track distribution advisories for package names, fixed versions, and reboot requirements.
  • Avoid mounting untrusted ext4 filesystems or disk images on production systems.
  • Use isolation for forensic or customer-supplied filesystem images.
  • Prioritize systems where ext4 availability directly supports critical services.

Validation and detection

  • Inventory Linux kernel versions and ext4 usage across servers and appliances.
  • Compare running kernels against vendor fixed packages or cited stable commits.
  • Review crash logs for ext4_read_inline_folio or BUG_ON-related panics.
  • After patching, confirm affected systems boot into the updated kernel.
  • Monitor logs for ext4_error_inode or filesystem corruption reports.
Prepared
Confidence
medium
Sources
10

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-2026-31451 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
0ADP providers
9Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux46c7f254543dedcf134ad05091ed2b935a9a597d, 46c7f254543dedcf134ad05091ed2b935a9a597d, 46c7f254543dedcf134ad05091ed2b935a9a597d, 46c7f254543dedcf134ad05091ed2b935a9a597d, 46c7f254543dedcf134ad05091ed2b935a9a597d, 46c7f254543dedcf134ad05091ed2b935a9a597d, 46c7f254543dedcf134ad05091ed2b935a9a597d, 46c7f254543dedcf134ad05091ed2b935a9a597dunaffected
LinuxLinux3.8, 0, 5.10.260, 5.15.211, 6.1.177, 6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0affected
Weakness

CWE details

No CWE listed

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