VYPR
High severity7.1NVD Advisory· Published May 17, 2024· Updated Jun 1, 2026

CVE-2023-52682

CVE-2023-52682

Description

A race condition in the Linux kernel f2fs filesystem allows data corruption when handling compressed, non-encrypted inodes during garbage collection.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A race condition in the Linux kernel f2fs filesystem allows data corruption when handling compressed, non-encrypted inodes during garbage collection.

Vulnerability

The Linux kernel f2fs filesystem contains a race condition in the f2fs_inplace_write_data path. Specifically, when an inode is compressed but not encrypted, the kernel fails to call f2fs_wait_on_block_writeback(). This omission allows the garbage collection (GC) thread to perform out-of-order writes while a page writeback is in progress, leading to potential data inconsistency [1].

Exploitation

An attacker requires local access to a system utilizing the f2fs filesystem with compression enabled. Exploitation involves triggering a race condition between the GC thread and a standard write operation on a compressed, non-encrypted file. By timing the f2fs_inplace_write_data operation to coincide with the GC thread's move_data_block execution, an attacker can cause the kernel to process overlapping IO requests, resulting in stale data overriding newer data [1].

Impact

Successful exploitation of this vulnerability leads to data corruption within the f2fs filesystem. This can result in the loss of data integrity for files stored on the affected partition, potentially impacting system stability or the reliability of stored information [1].

Mitigation

This issue was resolved in the Linux kernel by ensuring f2fs_wait_on_block_writeback() is called during the IPU write path for compressed inodes. Users should update to a patched kernel version, such as 6.8.10, 6.6.31, or later versions where this fix has been backported [1].

AI Insight generated on Jun 1, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

5

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

5

News mentions

0

No linked articles in our index yet.