# CVE-2023-52682: f2fs: fix to wait on block writeback for post_read case

> A race condition in the f2fs filesystem allows out-of-order garbage collection to overwrite new data with old data, requiring compressed but unencrypted inodes.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 May 2024
- **Updated:** 1 Jun 2026
- **Also known as:** BELL-CVE-2023-52682, DEBIAN-CVE-2023-52682, GHSA-gh7x-5rqw-m74q, ROOT-OS-DEBIAN-11-CVE-2023-52682, ROOT-OS-UBUNTU-2204-CVE-2023-52682, UBUNTU-CVE-2023-52682

## What is CVE-2023-52682?

CVE-2023-52682 is a high-severity vulnerability in Linux kernel, published on 17 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to wait on block writeback for post_read case

If inode is compressed, but not encrypted, it missed to call
f2fs_wait_on_block_writeback() to wait for GCed page writeback
in IPU write path.

Thread A				GC-Thread
					- f2fs_gc
					 - do_garbage_collect
					  - gc_data_segment
					   - move_data_block
					    - f2fs_submit_page_write
					     migrate normal cluster's block via
					     meta_inode's page cache
- f2fs_write_single_data_page
 - f2fs_do_write_data_page
  - f2fs_inplace_write_data
   - f2fs_submit_page_bio

IRQ
- f2fs_read_end_io
					IRQ
					old data overrides new data due to
					out-of-order GC and common IO.
					- f2fs_read_end_io

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2023-52682?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52682?

Apply the vendor's patch.

## Is CVE-2023-52682 being exploited?

There is no known exploitation of CVE-2023-52682 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52682 and fix it if it is affected.

What it is: CVE-2023-52682 is a high-severity vulnerability in Linux kernel, published on 17 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52682 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-52682/ (Markdown: https://insights.sbomify.com/CVE-2023-52682/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52682
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52682
- OSV: https://osv.dev/vulnerability/CVE-2023-52682

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52682/
Summaries are generated and may contain mistakes; the official description above is the record.