# CVE-2025-38333: f2fs: fix to bail out in get_new_segment()

> A flaw in the Linux kernel's f2fs filesystem allows a local attacker to trigger a kernel warning and potential denial of service via inconsistent segment maps.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 10 Jul 2025
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-64889, BELL-CVE-2025-38333, DEBIAN-CVE-2025-38333, GHSA-9ff3-g52h-6rx4, ROOT-OS-DEBIAN-11-CVE-2025-38333, ROOT-OS-DEBIAN-12-CVE-2025-38333, ROOT-OS-UBUNTU-2204-CVE-2025-38333, ROOT-OS-UBUNTU-2404-CVE-2025-38333, UBUNTU-CVE-2025-38333

## What is CVE-2025-38333?

CVE-2025-38333 is a high-severity denial of service vulnerability in Linux kernel, published on 10 Jul 2025. 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 bail out in get_new_segment()

------------[ cut here ]------------
WARNING: CPU: 3 PID: 579 at fs/f2fs/segment.c:2832 new_curseg+0x5e8/0x6dc
pc : new_curseg+0x5e8/0x6dc
Call trace:
 new_curseg+0x5e8/0x6dc
 f2fs_allocate_data_block+0xa54/0xe28
 do_write_page+0x6c/0x194
 f2fs_do_write_node_page+0x38/0x78
 __write_node_page+0x248/0x6d4
 f2fs_sync_node_pages+0x524/0x72c
 f2fs_write_checkpoint+0x4bc/0x9b0
 __checkpoint_and_complete_reqs+0x80/0x244
 issue_checkpoint_thread+0x8c/0xec
 kthread+0x114/0x1bc
 ret_from_fork+0x10/0x20

get_new_segment() detects inconsistent status in between free_segmap
and free_secmap, let's record such error into super block, and bail
out get_new_segment() instead of continue using the segment.

## Which versions are affected by CVE-2025-38333?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-38333?

Apply the vendor's patch.

## Is CVE-2025-38333 being exploited?

There is no known exploitation of CVE-2025-38333 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-2025-38333 and fix it if it is affected.

What it is: CVE-2025-38333 is a high-severity denial of service vulnerability in Linux kernel, published on 10 Jul 2025. 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-2025-38333 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-2025-38333/ (Markdown: https://insights.sbomify.com/CVE-2025-38333/index.md)
```

## Sources

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

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