Answer in brief
CVE-2023-54068 records a High severity (CVSS 7.8) vulnerability in f2fs: compress: fix to call f2fs_wait_on_page_writeback() in f2fs_write_raw_pages(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <a8226a45b2a9ce83ba7a167a387a00fecc319e71 || >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <169134da419cb8ffbe3b0743bc24573e16952ea9 || >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <6604df2a9d07ba8f8fb1ac14046c2c83776faa4f || >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <9940877c4fe752923a53f0f7372f2f152b6eccf0 || >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <ad31eed06c3b4d63b2d38322a271d4009aee4bb3 || >=4c8ff7095bef64fc47e996a938f7d57f9e077da3 <babedcbac164cec970872b8097401ca913a80e61 | a8226a45b2a9ce83ba7a167a387a00fecc319e71, 169134da419cb8ffbe3b0743bc24573e16952ea9, 6604df2a9d07ba8f8fb1ac14046c2c83776faa4f, 9940877c4fe752923a53f0f7372f2f152b6eccf0, ad31eed06c3b4d63b2d38322a271d4009aee4bb3, babedcbac164cec970872b8097401ca913a80e61 |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.