Menu

Star on GitHub · 3.2k

CVE-2025-38333

7.8 · HIGH

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:2…

Published Jul 10, 2025EPSS 0.18%

Overview

CVE-2025-38333 is a high-severity vulnerability. It was published on July 10, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-38333?

CVE-2025-38333 is a high-severity vulnerability. It was published on July 10, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-38333?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-38333?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-38333?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-38333 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all