Exploit Total
ExploreInsightsHow it worksContact us
bySign in

© 2026 Anyday Security

FAQPrivacy PolicyTerms of Use

Product names, logos and brands are property of their respective owners. They are used here for identification only and imply no affiliation or endorsement.

ExploreInsightsHow it worksContact us
Back
Vulnerability ID

CVE-2026-31448

Infinite loop in ext4

ProductLinux kernel
CVSS 3.1Critical9.4
EPSS0.50%
Has public PoCNo
AI Exploitability

No working AI exploit yet

Working AI PoC
Not yet
Cheapest run
$6.16
Fastest run
—
Model MatrixCapability BreakdownVulnerability DetailsTimelineCommunity
Sign in
Model MatrixCapability BreakdownVulnerability DetailsTimelineCommunity

Overview

View on NVD

ext4: avoid infinite loops caused by residual data On the mkdir/mknod path, when mapping logical blocks to physical blocks, if inserting a new extent into the extent tree fails (in this example, because the file system disabled the huge file feature when marking the inode as dirty), ext4_ext_map_blocks() only calls ext4_free_blocks() to reclaim the physical block without deleting the corresponding data in the extent tree. This causes subsequent mkdir operations to reference the previously reclaimed physical block number again, even though this physical block is already being used by the xattr block.

CWE
CWE-835
Weakness
Loop with Unreachable Exit Condition ('Infinite Loop')
Component
ext4
Impact
Not stated
Published
2026-04-22
Fixed version
7.0

Risk factors

In-the-WildNot observed
CISA KEVNot listed
Public ExploitNone known
Ransomware useNone known

Severity

CVSS 3.1Only version published

9.4Critical

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Exploitability
Attack VectorNetwork
ComplexityLow
Privileges RequiredNone
User InteractionNone
Impact
ConfidentialityLow
IntegrityHigh
AvailabilityHigh

EPSS

Chance of exploitation in the next 30 days

0.50%

SSVC

Stakeholder-specific vulnerability categorization

Not scored. CISA publishes an SSVC decision for a subset of CVEs.