CVE-2025-38333

What it actually does

Race condition in f2fs get_new_segment() allows inconsistent state between free_segmap and free_secmap, triggering kernel WARNING during new_curseg() and subsequent node page writes/checkpoints instead of safely bailing out with error recorded in superblock.

Why it matters to the business

Linux systems using f2fs may experience kernel warnings, checkpoint failures, or filesystem instability during heavy write workloads, increasing operational risk for storage-dependent services until patched; fixed versions available for affected Alpaquita linux-lts packages.

How an attack unfolds

An attacker with local access triggers concurrent f2fs allocation and checkpoint operations that race on segment maps, causing the kernel to hit the inconsistent-state path in new_curseg() and surface the warning; no public exploits or threat actors are associated.

How to fix it

Upgrade linux-lts (Alpaquita:23) to 6.1.81-r0 or later, linux-lts (Alpaquita:stream) to 6.6.58-r0 or 6.12.41-r0 or later, and mainline kernels to commit f0023d7a2a86999c8e1300e911d92f995a5310a8 or later; rebuild and reboot affected systems.

How to confirm the fix worked

Confirm kernel version matches or exceeds the listed fixed releases; run f2fs filesystem stress tests that exercise checkpoints and verify absence of the new_curseg WARNING; inspect superblock for recorded segment errors post-upgrade.

Typical attack path

1. Obtain local code execution on f2fs-formatted system
2. Induce concurrent data writes and fsync/checkpoint activity
3. Trigger segment allocation while maps are inconsistent
4. Observe kernel WARNING and potential write failure

How to detect it

Search kernel logs for the exact WARNING at fs/f2fs/segment.c:2832 new_curseg and the call trace involving f2fs_allocate_data_block, f2fs_write_checkpoint, and issue_checkpoint_thread; correlate with f2fs mount times and heavy write activity.

• WARNING: CPU:.*PID:.*at fs/f2fs/segment.c:2832 new_curseg
• new_curseg+0x5e8/0x6dc
• f2fs_allocate_data_block+0xa54/0xe28

What your security team should do

• Prioritize patching production f2fs systems within standard change windows given low EPSS but kernel stability impact
• Monitor EPSS trend for any increase above 0.01 before accelerating
• Add f2fs checkpoint and segment allocation logs to security monitoring for the WARNING pattern