CVE-2023-53845

nilfs2: fix infinite loop in nilfs_mdt_get_block()

N/A
Published: December 9, 2025 at 01:30 AM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.3%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.30 ≤ v < 4.14.3152.6.30 ≤ v < 4.19.2832.6.30 ≤ v < 5.10.1802.6.30 ≤ v < 5.15.1112.6.30 ≤ v < 5.4.2432.6.30 ≤ v < 6.1.282.6.30 ≤ v < 6.2.152.6.30 ≤ v < 6.3.22.6.30 ≤ v < 6.42.6.30bdb265eae08db578e7cf5739be16f389d495fc75
Vendor states this is fixed in 25457d07c8146e57d28906c663def033dc425af6 (fixed)
Vendor states this is fixed in 34c5f17222b50c79848bb03ec8811648813e6a45 (fixed)
Vendor states this is fixed in 5b29661669cb65b9750a3cf70ed3eaf947b92167 (fixed)
Vendor states this is fixed in 8a89d36a07afe1ed4564df51fefa2bb556c85412 (fixed)
Vendor states this is fixed in 8d07d9119642ba43d21f8ba64d51d01931096b20 (fixed)
Vendor states this is fixed in a6a491c048882e7e424d407d32cba0b52d9ef2bf (fixed)
Vendor states this is fixed in cfb0bb4fbd40c1f06da7e9f88c0a2d46155b90c2 (fixed)
Vendor states this is fixed in d536f9976bb04e9c84cf80045a9355975e418f41 (fixed)
Vendor states this is fixed in fe1cbbcb1a2532ee1654e1ff121be8906d83c6f0 (fixed)
Vendor states this is fixed in 2.6.30 (unaffected)
Vendor states this is fixed in 4.14.315 (unaffected)
Vendor states this is fixed in 4.19.283 (unaffected)
Vendor states this is fixed in 5.10.180 (unaffected)
Vendor states this is fixed in 5.15.111 (unaffected)
Vendor states this is fixed in 5.4.243 (unaffected)
Vendor states this is fixed in 6.1.28 (unaffected)
Vendor states this is fixed in 6.2.15 (unaffected)
Vendor states this is fixed in 6.3.2 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card