CVE-2023-54068

f2fs: compress: fix to call f2fs_wait_on_page_writeback() in f2fs_write_raw_pages()

State
Published
Severity
7.8 High
Published
Dec 24, 2025
Updated
Aug 5, 2026
Reserved
Dec 24, 2025

Read the record on cve.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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before a8226a45b2a9ce83ba7a167a387a00fecc319e71Affected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before 169134da419cb8ffbe3b0743bc24573e16952ea9Affected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before 6604df2a9d07ba8f8fb1ac14046c2c83776faa4fAffected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before 9940877c4fe752923a53f0f7372f2f152b6eccf0Affected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before ad31eed06c3b4d63b2d38322a271d4009aee4bb3Affected
  • 4c8ff7095bef64fc47e996a938f7d57f9e077da3 to before babedcbac164cec970872b8097401ca913a80e61Affected
LinuxLinux
  • 5.6Affected
  • before 5.6Not affected
  • 5.10.180 through 5.10.*Not affected
  • 5.15.111 through 5.15.*Not affected
  • 6.1.28 through 6.1.*Not affected
  • 6.2.15 through 6.2.*Not affected
  • 6.3.2 through 6.3.*Not affected
  • 6.4 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.