Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-53845

nilfs2: fix infinite loop in nilfs_mdt_get_block()

Not scoredEPSS 0.26%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix infinite loop in nilfs_mdt_get_block() If the disk image that nilfs2 mounts is corrupted and a virtual block address obtained by block lookup for a metadata file is invalid, nilfs_bmap_lookup_at_level() may return the same internal return code as -ENOENT, meaning the block does not exist in the metadata file. This duplication of return codes confuses nilfs_mdt_get_block(), causing it to read and create a metadata block indefinitely. In particular, if this happens to the inode metadata file, ifile, semaphore i_rwsem can be left held, causing task hangs in lock_mount. Fix this issue by making nilfs_bmap_lookup_at_level() treat virtual block address translation failures with -ENOENT as metadata corruption instead of returning the error code.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.26% · top 83% of all CVEs (7 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected bdb265eae08db578e7cf5739be16f389d495fc75 – < cfb0bb4fbd40c1f06da7e9f88c0a2d46155b90c2
    • affected bdb265eae08db578e7cf5739be16f389d495fc75 – < d536f9976bb04e9c84cf80045a9355975e418f41
    • affected bdb265eae08db578e7cf5739be16f389d495fc75 – < fe1cbbcb1a2532ee1654e1ff121be8906d83c6f0
    • affected bdb265eae08db578e7cf5739be16f389d495fc75 – < 8a89d36a07afe1ed4564df51fefa2bb556c85412
    • affected bdb265eae08db578e7cf5739be16f389d495fc75 – < 8d07d9119642ba43d21f8ba64d51d01931096b20
    • affected bdb265eae08db578e7cf5739be16f389d495fc75 – < 25457d07c8146e57d28906c663def033dc425af6
    • affected bdb265eae08db578e7cf5739be16f389d495fc75 – < 34c5f17222b50c79848bb03ec8811648813e6a45
    • affected bdb265eae08db578e7cf5739be16f389d495fc75 – < 5b29661669cb65b9750a3cf70ed3eaf947b92167
    • affected bdb265eae08db578e7cf5739be16f389d495fc75 – < a6a491c048882e7e424d407d32cba0b52d9ef2bf
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 4.14.315 – ≤ 4.14.*
    • unaffected 4.19.283 – ≤ 4.19.*
    • unaffected 5.4.243 – ≤ 5.4.*
    • unaffected 5.10.180 – ≤ 5.10.*
    • unaffected 5.15.111 – ≤ 5.15.*
    • unaffected 6.1.28 – ≤ 6.1.*
    • unaffected 6.2.15 – ≤ 6.2.*
    • unaffected 6.3.2 – ≤ 6.3.*
    • unaffected 6.4 – ≤ *

References (9)

Sources

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

Badge for a README or a ticket

CVE-2023-53845 badge
[![CVE-2023-53845](https://trackcve.app/badge/CVE-2023-53845.svg)](https://trackcve.app/cve/CVE-2023-53845)

Record last updated .