CVE-2023-54068
Unknown Unknown - Not Provided
Use-After-Free in Linux f2fs Compression Causes Kernel BUG

Publication date: 2025-12-24

Last updated on: 2025-12-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix to call f2fs_wait_on_page_writeback() in f2fs_write_raw_pages() BUG_ON() will be triggered when writing files concurrently, because the same page is writtenback multiple times. 1597 void folio_end_writeback(struct folio *folio) 1598 { ...... 1618 if (!__folio_end_writeback(folio)) 1619 BUG(); ...... 1625 } kernel BUG at mm/filemap.c:1619! Call Trace: <TASK> f2fs_write_end_io+0x1a0/0x370 blk_update_request+0x6c/0x410 blk_mq_end_request+0x15/0x130 blk_complete_reqs+0x3c/0x50 __do_softirq+0xb8/0x29b ? sort_range+0x20/0x20 run_ksoftirqd+0x19/0x20 smpboot_thread_fn+0x10b/0x1d0 kthread+0xde/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> Below is the concurrency scenario: [Process A] [Process B] [Process C] f2fs_write_raw_pages() - redirty_page_for_writepage() - unlock page() f2fs_do_write_data_page() - lock_page() - clear_page_dirty_for_io() - set_page_writeback() [1st writeback] ..... - unlock page() generic_perform_write() - f2fs_write_begin() - wait_for_stable_page() - f2fs_write_end() - set_page_dirty() - lock_page() - f2fs_do_write_data_page() - set_page_writeback() [2st writeback] This problem was introduced by the previous commit 7377e853967b ("f2fs: compress: fix potential deadlock of compress file"). All pagelocks were released in f2fs_write_raw_pages(), but whether the page was in the writeback state was ignored in the subsequent writing process. Let's fix it by waiting for the page to writeback before writing.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-24
Last Modified
2025-12-24
Generated
2026-05-07
AI Q&A
2025-12-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the Linux kernel's f2fs filesystem occurs because the function f2fs_write_raw_pages() does not properly wait for a page to finish writeback before attempting to write it again. This leads to a kernel BUG_ON() being triggered when files are written concurrently, as the same page is written back multiple times simultaneously. The issue was introduced by a previous commit that released all page locks without checking if the page was still in writeback state. The fix involves calling f2fs_wait_on_page_writeback() to ensure the page writeback completes before proceeding with another write.


How can this vulnerability impact me? :

This vulnerability can cause the Linux kernel to crash (kernel BUG) during concurrent file writes on the f2fs filesystem, leading to system instability or downtime. Such crashes can result in data loss or corruption and disrupt normal system operations.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring for kernel BUG messages related to f2fs writeback errors, specifically kernel BUG at mm/filemap.c:1619. You can check the kernel logs for such BUG_ON() triggers using commands like 'dmesg | grep BUG' or 'journalctl -k | grep BUG'. Additionally, monitoring for system crashes or kernel panics during concurrent file writes on f2fs file systems may indicate this issue.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, as the issue is resolved by calling f2fs_wait_on_page_writeback() in f2fs_write_raw_pages(). Until an update is applied, avoid concurrent writes to files on f2fs file systems to prevent triggering the BUG_ON().


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart