Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31448ext4: avoid infinite loops caused by residual data

Description

In the Linux kernel, the following vulnerability has been resolved: 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. Therefore, a situation arises where both the directory and xattr are using the same buffer head block in memory simultaneously. The above causes ext4_xattr_block_set() to enter an infinite loop about "inserted" and cannot release the inode lock, ultimately leading to the 143s blocking problem mentioned in [1]. If the metadata is corrupted, then trying to remove some extent space can do even more harm. Also in case EXT4_GET_BLOCKS_DELALLOC_RESERVE was passed, remove space wrongly update quota information. Jan Kara suggests distinguishing between two cases: 1) The error is ENOSPC or EDQUOT - in this case the filesystem is fully consistent and we must maintain its consistency including all the accounting. However these errors can happen only early before we've inserted the extent into the extent tree. So current code works correctly for this case. 2) Some other error - this means metadata is corrupted. We should strive to do as few modifications as possible to limit damage. So I'd just skip freeing of allocated blocks. [1] INFO: task syz.0.17:5995 blocked for more than 143 seconds. Call Trace: inode_lock_nested include/linux/fs.h:1073 [inline] __start_dirop fs/namei.c:2923 [inline] start_dirop fs/namei.c:2934 [inline]

Timeline

  1. ID reserved

    By Linux

  2. · 44 days later

    Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31448, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.4CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
NVDNVD · Modified3.1Critical9.4CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
EPSS (exploitation in 30 days)
0.50% · top 57% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.4.

Affected products

  • Linux · Linux

    • affected 315054f023d28ee64f308adf8b5737831541776b – < c66545e83a802c3851d9be27a41c0479dd29ff0c
    • affected 315054f023d28ee64f308adf8b5737831541776b – < ecc50bfca9b5c2ee6aeef998181689b80477367b
    • affected 315054f023d28ee64f308adf8b5737831541776b – < 3a7667595bcad84da53fc156a418e110267c3412
    • affected 315054f023d28ee64f308adf8b5737831541776b – < 416c86f30f91b4fb2642ef6b102596ca898f41a5
    • affected 315054f023d28ee64f308adf8b5737831541776b – < 64f425b06b3bea9abc8977fd3982779b3ad070c9
    • affected 315054f023d28ee64f308adf8b5737831541776b – < 5422fe71d26d42af6c454ca9527faaad4e677d6c
  • Linux · Linux

    • affected 2.6.22
    • unaffected < 2.6.22
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31448 badge
[![CVE-2026-31448](https://cveledger.app/badge/CVE-2026-31448.svg)](https://cveledger.app/cve/CVE-2026-31448)

Record last updated .