LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71107: f2fs: ensure node page reads complete before f2fs_put_super() finishes

In the Linux kernel, the following vulnerability has been resolved: f2fs: ensure node page reads complete before f2fs_put_super() finishes Xfstests generic/335, generic/336 sometimes crash with the following message: F2FS-fs (dm-0): detect filesystem reference count leak during umount, type: 9, count: 1 ------------[ cut here ]------------ kernel BUG at fs/f2fs/super.c:1939! Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 609351 Comm: umount Tainted: G W 6.17.0-rc5-xfstests-g9dd1835ecda5 #1 PREEMPT(none) Tainted: [W]=WARN Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:f2fs_put_super+0x3b3/0x3c0 Call Trace: <TASK> generic_shutdown_super+0x7e/0x190 kill_block_super+0x1a/0x40 kill_f2fs_super+0x9d/0x190 deactivate_locked_super+0x30/0xb0 cleanup_mnt+0xba/0x150 task_work_run+0x5c/0xa0 exit_to_user_mode_loop+0xb7/0xc0 do_syscall_64+0x1ae/0x1c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e </TASK> ---[ end trace 0000000000000000 ]--- It appears that sometimes it is possible that f2fs_put_super() is called before all node page reads are completed. Adding a call to f2fs_wait_on_all_pages() for F2FS_RD_NODE fixes the problem.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel F2FS bug that can crash the kernel during unmount when pending node page reads have not finished. The public record shows failures in filesystem testing, not active exploitation. Business impact is mainly availability risk on systems that use F2FS and run affected kernels.

Executive priority

Treat as a targeted availability issue, not an emergency internet-scale exposure based on current evidence. Prioritize patching where F2FS is used in production, embedded, mobile, or storage-sensitive Linux environments.

Technical view

F2FS f2fs_put_super() could complete while F2FS_RD_NODE page reads were still outstanding, causing a filesystem reference count leak and kernel BUG during unmount. The stated fix adds f2fs_wait_on_all_pages() for F2FS_RD_NODE before teardown completes.

Likely exposure

Exposure appears limited to Linux systems using the F2FS filesystem on affected kernel versions or builds lacking the referenced stable fixes. Systems not using F2FS are unlikely to be exposed based on the provided record.

Exploitation context

The source bundle reports crashes during xfstests generic/335 and generic/336. It provides no evidence of public exploitation, KEV listing, remote attack path, privilege escalation, or weaponized exploit availability.

Researcher notes

The record does not include CVSS, CWE, exploitability analysis, or distribution advisories. Affected version data is commit-oriented and uneven, so validation should use vendor kernel advisories and the referenced stable commits rather than version strings alone.

Mitigation direction

  • Inventory Linux systems using F2FS filesystems.
  • Prioritize affected F2FS systems with high availability requirements.
  • Apply vendor or distribution kernel updates containing the referenced stable fixes.
  • If updates are unavailable, monitor vendor guidance before changing production behavior.

Validation and detection

  • Confirm whether hosts mount or manage F2FS volumes.
  • Compare kernel build lineage against the CVE affected versions and fix commits.
  • Review kernel logs for F2FS reference count leak messages during unmount.
  • Confirm patched kernels include the F2FS_RD_NODE wait fix.
Prepared
Confidence
medium
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-71107 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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
LinuxLinux20872584b8c0b006c007da9588a272c9e28d2e18, 20872584b8c0b006c007da9588a272c9e28d2e18, 20872584b8c0b006c007da9588a272c9e28d2e18, 20872584b8c0b006c007da9588a272c9e28d2e18, 0e2577074b459bba7f4016f4d725ede37d48bb22, 6.4.16unaffected
LinuxLinux6.5, 0, 6.6.120, 6.12.64, 6.18.3, 6.19affected
Weakness

CWE details

No CWE listed

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