CVE-2023-54068

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

HIGH
7.8
CVSS Score
Published: December 24, 2025 at 12:23 PM UTC
Updated: August 5, 2026 at 10:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.6 ≤ v < 5.10.1805.6 ≤ v < 5.15.1115.6 ≤ v < 6.1.285.6 ≤ v < 6.2.155.6 ≤ v < 6.3.25.6 ≤ v < 6.44c8ff7095bef64fc47e996a938f7d57f9e077da35.6
Vendor states this is fixed in 169134da419cb8ffbe3b0743bc24573e16952ea9 (fixed)
Vendor states this is fixed in 6604df2a9d07ba8f8fb1ac14046c2c83776faa4f (fixed)
Vendor states this is fixed in 9940877c4fe752923a53f0f7372f2f152b6eccf0 (fixed)
Vendor states this is fixed in a8226a45b2a9ce83ba7a167a387a00fecc319e71 (fixed)
Vendor states this is fixed in ad31eed06c3b4d63b2d38322a271d4009aee4bb3 (fixed)
Vendor states this is fixed in babedcbac164cec970872b8097401ca913a80e61 (fixed)
Vendor states this is fixed in 5.10.180 (unaffected)
Vendor states this is fixed in 5.15.111 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.28 (unaffected)
Vendor states this is fixed in 6.2.15 (unaffected)
Vendor states this is fixed in 6.3.2 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card