LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38164: f2fs: zone: fix to avoid inconsistence in between SIT and SSA

In the Linux kernel, the following vulnerability has been resolved: f2fs: zone: fix to avoid inconsistence in between SIT and SSA w/ below testcase, it will cause inconsistence in between SIT and SSA. create_null_blk 512 2 1024 1024 mkfs.f2fs -m /dev/nullb0 mount /dev/nullb0 /mnt/f2fs/ touch /mnt/f2fs/file f2fs_io pinfile set /mnt/f2fs/file fallocate -l 4GiB /mnt/f2fs/file F2FS-fs (nullb0): Inconsistent segment (0) type [1, 0] in SSA and SIT CPU: 5 UID: 0 PID: 2398 Comm: fallocate Tainted: G O 6.13.0-rc1 #84 Tainted: [O]=OOT_MODULE Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 Call Trace: <TASK> dump_stack_lvl+0xb3/0xd0 dump_stack+0x14/0x20 f2fs_handle_critical_error+0x18c/0x220 [f2fs] f2fs_stop_checkpoint+0x38/0x50 [f2fs] do_garbage_collect+0x674/0x6e0 [f2fs] f2fs_gc_range+0x12b/0x230 [f2fs] f2fs_allocate_pinning_section+0x5c/0x150 [f2fs] f2fs_expand_inode_data+0x1cc/0x3c0 [f2fs] f2fs_fallocate+0x3c3/0x410 [f2fs] vfs_fallocate+0x15f/0x4b0 __x64_sys_fallocate+0x4a/0x80 x64_sys_call+0x15e8/0x1b80 do_syscall_64+0x68/0x130 entry_SYSCALL_64_after_hwframe+0x67/0x6f RIP: 0033:0x7f9dba5197ca F2FS-fs (nullb0): Stopped filesystem due to reason: 4 The reason is f2fs_gc_range() may try to migrate block in curseg, however, its SSA block is not uptodate due to the last summary block data is still in cache of curseg. In this patch, we add a condition in f2fs_gc_range() to check whether section is opened or not, and skip block migration for opened section.

HighCVSS 7.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux F2FS flaw can make two filesystem metadata structures disagree during garbage collection on zoned storage. The kernel may then stop the filesystem to prevent further damage, disrupting services and risking metadata integrity. Exploitation requires local, low-privileged access; the supplied CVSS score is 7.1.

Executive priority

Prioritize remediation on production systems using F2FS zoned storage, especially where local users or workloads are not fully trusted. Treat other systems as lower urgency after confirming F2FS is absent. Because integrity and availability are affected, validate backups and recovery readiness alongside patch deployment.

Technical view

During f2fs_gc_range(), blocks in a currently open section may be migrated before its cached summary data updates the SSA. This can produce conflicting segment types in the SSA and SIT, trigger a critical filesystem error, and stop checkpointing. The kernel fix detects open sections and skips their block migration.

Likely exposure

Exposure is limited to systems using affected Linux kernels with F2FS, particularly zoned-storage configurations exercising garbage collection, pinned files, and allocation operations. The bundle marks Linux 6.9, 6.6.130, 6.12.34, 6.15.3, and 6.16 as affected; distribution backports may alter actual status.

Exploitation context

The CVSS vector indicates a local attack requiring low privileges, without user interaction. Successful triggering could affect filesystem integrity and availability, but not confidentiality. The supplied record is not in KEV and provides no evidence of active exploitation or a public weaponized exploit.

Researcher notes

The supplied testcase demonstrates metadata inconsistency and a defensive filesystem stop under Linux 6.13.0-rc1. Root cause is stale cached curseg summary data during migration from an open section. No CWE is assigned. Exact vulnerable introduction boundaries and distribution-specific backport status are not fully established by the bundle.

Mitigation direction

  • Apply a vendor-supported kernel update containing the relevant stable-branch fix.
  • Confirm distribution backports rather than relying only on the reported upstream version numbers.
  • Prioritize systems using F2FS on zoned storage or supporting untrusted local workloads.
  • If updates are unavailable, obtain interim risk-reduction guidance from the kernel or distribution vendor.

Validation and detection

  • Inventory kernel versions and identify systems mounting F2FS filesystems.
  • Determine whether affected F2FS volumes use zoned storage and pinned-file workflows.
  • Verify the installed kernel includes the applicable linked stable commit or vendor backport.
  • Review kernel logs for F2FS SSA/SIT inconsistency and stopped-filesystem messages.
  • Test updates safely in staging; do not reproduce the trigger on production data.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38164 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H1.85.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-38164Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux40d76c393cca83938b11eb7ca8983aa3cd0ed69b, 9703d69d9d153bb230711d0d577454552aeb13d4, 9703d69d9d153bb230711d0d577454552aeb13d4, 9703d69d9d153bb230711d0d577454552aeb13d4, 6.6.33unaffected
LinuxLinux6.9, 0, 6.6.130, 6.12.34, 6.15.3, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.