CVE-2023-53845

UnknownEPSS 0.22%

Last modified

CVE-2023-53845 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.22% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.22%

12.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= bdb265eae08db578e7cf5739be16f389d495fc75, < cfb0bb4fbd40c1f06da7e9f88c0a2d46155b90c2; >= bdb265eae08db578e7cf5739be16f389d495fc75, < d536f9976bb04e9c84cf80045a9355975e418f41; >= bdb265eae08db578e7cf5739be16f389d495fc75, < fe1cbbcb1a2532ee1654e1ff121be8906d83c6f0; >= bdb265eae08db578e7cf5739be16f389d495fc75, < 8a89d36a07afe1ed4564df51fefa2bb556c85412; >= bdb265eae08db578e7cf5739be16f389d495fc75, < 8d07d9119642ba43d21f8ba64d51d01931096b20; >= bdb265eae08db578e7cf5739be16f389d495fc75, < 25457d07c8146e57d28906c663def033dc425af6; >= bdb265eae08db578e7cf5739be16f389d495fc75, < 34c5f17222b50c79848bb03ec8811648813e6a45; >= bdb265eae08db578e7cf5739be16f389d495fc75, < 5b29661669cb65b9750a3cf70ed3eaf947b92167; >= bdb265eae08db578e7cf5739be16f389d495fc75, < a6a491c048882e7e424d407d32cba0b52d9ef2bf
LinuxLinux2.6.30

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2023-53845?
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.
How severe is CVE-2023-53845?
Severity scoring for CVE-2023-53845 is pending analysis. The EPSS model estimates a 0.22% probability of exploitation in the next 30 days.
How do I fix CVE-2023-53845?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2023

Are you affected by CVE-2023-53845?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST