Linux Kernel up to 6.3.2 f2fs ext4_rename denial of service

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel up to 6.3.2 and classified as critical. This affects the function ext4_rename of the component f2fs. This manipulation causes denial of service.
The identification of this vulnerability is CVE-2023-54187. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability was found in Linux Kernel up to 6.3.2. It has been declared as critical. Affected by this vulnerability is the function ext4_rename of the component f2fs. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix potential corruption when moving a directory F2FS has the same issue in ext4_rename causing crash revealed by xfstests/generic/707. See also commit 0813299c586b ("ext4: Fix possible corruption when moving a directory")
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2023-54187 since 12/30/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 281734 (Linux Distros Unpatched Vulnerability : CVE-2023-54187), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.4.243, 5.10.180, 5.15.112, 6.1.29, 6.2.16 or 6.3.3 eliminates this vulnerability. Applying the patch 3e77036246123ff710fa2661dcaa12a45284f09b/957904f531fd857a92743b11fbc9c9ffdf7f3207/8f57f3e112cf1d16682b6ff9c31c72f40f7da9c9/8a0b544b7caedfbc05065b6377fd1d8bf7ef5e70/f20191100952013f0916418cdaed0ab55c7b634c/0a76082a4a32a90d1ef33dee8b400efc082b4b6f/d94772154e524b329a168678836745d2773a6e02 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 vulnerability database at Tenable (281734). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 5.4.242
- 5.10.179
- 5.15.111
- 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.1.28
- 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.2.15
- 6.3.0
- 6.3.1
- 6.3.2
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: Denial of serviceCWE: 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: 281734
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-54187
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.4.243/5.10.180/5.15.112/6.1.29/6.2.16/6.3.3
Patch: 3e77036246123ff710fa2661dcaa12a45284f09b/957904f531fd857a92743b11fbc9c9ffdf7f3207/8f57f3e112cf1d16682b6ff9c31c72f40f7da9c9/8a0b544b7caedfbc05065b6377fd1d8bf7ef5e70/f20191100952013f0916418cdaed0ab55c7b634c/0a76082a4a32a90d1ef33dee8b400efc082b4b6f/d94772154e524b329a168678836745d2773a6e02
Timeline
12/30/2025 Advisory disclosed12/30/2025 CVE reserved
12/30/2025 VulDB entry created
01/05/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-54187 (🔒)
GCVE (CVE): GCVE-0-2023-54187
GCVE (VulDB): GCVE-100-338929
Entry
Created: 12/30/2025 16:30Updated: 01/05/2026 18:55
Changes: 12/30/2025 16:30 (59), 01/05/2026 18:55 (2)
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.