Linux Kernel up to 6.3.3 f2fs umount infinite loop

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.6$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 6.3.3. Affected is the function umount of the component f2fs. Performing a manipulation results in infinite loop. This vulnerability is cataloged as CVE-2023-54124. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.3.3. This affects the function umount of the component f2fs. The manipulation with an unknown input leads to a infinite loop vulnerability. CWE is classifying the issue as CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. This is going to have an impact on availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to drop all dirty pages during umount() if cp_error is set xfstest generic/361 reports a bug as below: f2fs_bug_on(sbi, sbi->fsync_node_num); kernel BUG at fs/f2fs/super.c:1627! RIP: 0010:f2fs_put_super+0x3a8/0x3b0 Call Trace: generic_shutdown_super+0x8c/0x1b0 kill_block_super+0x2b/0x60 kill_f2fs_super+0x87/0x110 deactivate_locked_super+0x39/0x80 deactivate_super+0x46/0x50 cleanup_mnt+0x109/0x170 __cleanup_mnt+0x16/0x20 task_work_run+0x65/0xa0 exit_to_user_mode_prepare+0x175/0x190 syscall_exit_to_user_mode+0x25/0x50 do_syscall_64+0x4c/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc During umount(), if cp_error is set, f2fs_wait_on_all_pages() should not stop waiting all F2FS_WB_CP_DATA pages to be writebacked, otherwise, fsync_node_num can be non-zero after f2fs_wait_on_all_pages() causing this bug. In this case, to avoid deadloop in f2fs_wait_on_all_pages(), it needs to drop all dirty pages rather than redirtying them.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2023-54124 since 12/24/2025. The exploitability is told to be difficult. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 280018 (Linux Distros Unpatched Vulnerability : CVE-2023-54124), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.19.284, 5.4.244, 5.10.181, 5.15.113, 6.1.30 or 6.3.4 eliminates this vulnerability. Applying the patch 92575f05a32dafb16348bfa5e62478118a9be069/4ceedc2f8bdffb82e40b7d1bb912304f8e157cb1/ad87bd313f70b51e48019d5ce2d02d73152356b3/d8f4ad5f3979dbd8e6251259562f12472717883a/7741ddc882a0c806a6508ba8203c55a779db7a21/82c3d6e9db41cbd3af1d4f90bdb441740b5fad10/c9b3649a934d131151111354bcbb638076f03a30 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 (280018) and CERT Bund (WID-SEC-2025-2929). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Infinite loop
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 280018
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-54124

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.19.284/5.4.244/5.10.181/5.15.113/6.1.30/6.3.4
Patch: 92575f05a32dafb16348bfa5e62478118a9be069/4ceedc2f8bdffb82e40b7d1bb912304f8e157cb1/ad87bd313f70b51e48019d5ce2d02d73152356b3/d8f4ad5f3979dbd8e6251259562f12472717883a/7741ddc882a0c806a6508ba8203c55a779db7a21/82c3d6e9db41cbd3af1d4f90bdb441740b5fad10/c9b3649a934d131151111354bcbb638076f03a30

Timelineinfo

12/24/2025 Advisory disclosed
12/24/2025 +0 days CVE reserved
12/24/2025 +0 days VulDB entry created
01/03/2026 +10 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-54124 (🔒)
GCVE (CVE): GCVE-0-2023-54124
GCVE (VulDB): GCVE-100-338139
CERT Bund: WID-SEC-2025-2929 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 12/24/2025 15:15
Updated: 01/03/2026 04:20
Changes: 12/24/2025 15:15 (59), 12/27/2025 15:34 (2), 01/03/2026 04:20 (7)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!