LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26869: f2fs: fix to truncate meta inode pages forcely

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to truncate meta inode pages forcely Below race case can cause data corruption: Thread A GC thread - gc_data_segment - ra_data_block - locked meta_inode page - f2fs_inplace_write_data - invalidate_mapping_pages : fail to invalidate meta_inode page due to lock failure or dirty|writeback status - f2fs_submit_page_bio : write last dirty data to old blkaddr - move_data_block - load old data from meta_inode page - f2fs_submit_page_write : write old data to new blkaddr Because invalidate_mapping_pages() will skip invalidating page which has unclear status including locked, dirty, writeback and so on, so we need to use truncate_inode_pages_range() instead of invalidate_mapping_pages() to make sure meta_inode page will be dropped.

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

Security readout for executives and security teams

Plain-English summary

A race condition in Linux F2FS can preserve stale filesystem metadata while data is relocated, potentially writing old data to a new storage location and causing corruption. Exploitation requires local access according to the supplied CVSS vector. Systems not using F2FS are unlikely to be exposed.

Executive priority

Treat as a high-priority integrity and availability issue where F2FS supports important workloads. Patch through normal emergency kernel processes after confirming exposure. Lower the priority for systems that do not use F2FS. Current evidence does not justify describing this as actively exploited.

Technical view

During an in-place write, invalidate_mapping_pages() can skip a locked, dirty, or writeback meta-inode page while garbage collection relocates its data. The stale page may then supply old data to the new block address. Stable kernel fixes use truncate_inode_pages_range() to ensure the affected metadata page is dropped.

Likely exposure

Exposure is limited to Linux systems using F2FS and running an affected, unpatched kernel. The bundle lists affected version entries from 4.19 through 6.9, but does not encode the precise version ranges clearly. Distribution backports may change actual exposure.

Exploitation context

The supplied CVSS 3.1 vector rates this as local, low-complexity, low-privilege, and requiring no user interaction. Neither the provided sources nor the KEV status establish active exploitation. The documented mechanism is a filesystem race causing data corruption; reliable attacker control is not demonstrated.

Researcher notes

The central issue is incomplete invalidation semantics under concurrent F2FS garbage collection and in-place writes. The source demonstrates a corruption race and provides four stable commits, but does not demonstrate exploit reliability, attacker-directed disclosure, or precise distribution-specific affected ranges. Validate backports rather than relying only on upstream version numbers.

Mitigation direction

  • Install a vendor-supported kernel update containing the applicable cited F2FS stable fix.
  • Check distribution advisories or kernel changelogs to confirm whether the fix was backported.
  • Prioritize affected F2FS systems holding sensitive, operationally critical, or difficult-to-recover data.
  • Maintain verified backups before kernel maintenance and follow vendor guidance for recovery precautions.

Validation and detection

  • Inventory kernel versions and identify hosts that actively use or mount F2FS filesystems.
  • Compare vendor kernel changelogs against the cited stable commits or an explicit CVE-2024-26869 reference.
  • Confirm the updated kernel is running after remediation, not merely installed.
  • Review filesystem integrity and system logs for corruption symptoms using approved operational procedures.
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-2024-26869 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

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.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-26869Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6aa58d8ad20a3323f42274c25820a6f54192422d, 6aa58d8ad20a3323f42274c25820a6f54192422d, 6aa58d8ad20a3323f42274c25820a6f54192422d, 6aa58d8ad20a3323f42274c25820a6f54192422dunaffected
LinuxLinux4.19, 0, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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