Linux Kernel up to 6.3.1 nilfs_mdt_get_block infinite loop

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Linux Kernel up to 6.3.1. The affected element is the function nilfs_mdt_get_block. The manipulation leads to infinite loop.
This vulnerability is listed as CVE-2023-53845. There is no available exploit.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 6.3.1. It has been rated as critical. This issue affects the function nilfs_mdt_get_block. The manipulation with an unknown input leads to a infinite loop vulnerability. Using CWE to declare the problem leads to CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Impacted is availability. The summary by CVE is:
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.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2023-53845 since 12/09/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 278356 (Linux Distros Unpatched Vulnerability : CVE-2023-53845), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.14.315, 4.19.283, 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15 or 6.3.2 eliminates this vulnerability. Applying the patch cfb0bb4fbd40c1f06da7e9f88c0a2d46155b90c2/d536f9976bb04e9c84cf80045a9355975e418f41/fe1cbbcb1a2532ee1654e1ff121be8906d83c6f0/8a89d36a07afe1ed4564df51fefa2bb556c85412/8d07d9119642ba43d21f8ba64d51d01931096b20/25457d07c8146e57d28906c663def033dc425af6/34c5f17222b50c79848bb03ec8811648813e6a45/5b29661669cb65b9750a3cf70ed3eaf947b92167/a6a491c048882e7e424d407d32cba0b52d9ef2bf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (278356) and CERT Bund (WID-SEC-2025-2765). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- Open Source Linux Kernel
- RESF Rocky Linux
Product
Type
Vendor
Name
Version
- 4.14.314
- 4.19.282
- 5.4.242
- 5.10.179
- 5.15.110
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.2.0
- 6.2.1
- 6.2.2
- 6.2.3
- 6.2.4
- 6.2.5
- 6.2.6
- 6.2.7
- 6.2.8
- 6.2.9
- 6.2.10
- 6.2.11
- 6.2.12
- 6.2.13
- 6.2.14
- 6.3.0
- 6.3.1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Infinite loopCWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 278356
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-53845
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.14.315/4.19.283/5.4.243/5.10.180/5.15.111/6.1.28/6.2.15/6.3.2
Patch: cfb0bb4fbd40c1f06da7e9f88c0a2d46155b90c2/d536f9976bb04e9c84cf80045a9355975e418f41/fe1cbbcb1a2532ee1654e1ff121be8906d83c6f0/8a89d36a07afe1ed4564df51fefa2bb556c85412/8d07d9119642ba43d21f8ba64d51d01931096b20/25457d07c8146e57d28906c663def033dc425af6/34c5f17222b50c79848bb03ec8811648813e6a45/5b29661669cb65b9750a3cf70ed3eaf947b92167/a6a491c048882e7e424d407d32cba0b52d9ef2bf
Timeline
12/09/2025 Advisory disclosed12/09/2025 CVE reserved
12/09/2025 VulDB entry created
03/30/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-53845 (🔒)
GCVE (CVE): GCVE-0-2023-53845
GCVE (VulDB): GCVE-100-335033
CERT Bund: WID-SEC-2025-2765 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 12/09/2025 11:11Updated: 03/30/2026 02:12
Changes: 12/09/2025 11:11 (58), 12/12/2025 04:18 (2), 03/30/2026 02:12 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.