Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 58 days later

    Published

  3. · 3 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-26869, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 6aa58d8ad20a3323f42274c25820a6f54192422d – < 0721a4f85d12a364002a9476c84b930fbc993f83
    • affected 6aa58d8ad20a3323f42274c25820a6f54192422d – < c92f2927df860a60ba815d3ee610a944b92a8694
    • affected 6aa58d8ad20a3323f42274c25820a6f54192422d – < 77bfdb89cc222fc7bfe198eda77bdc427d5ac189
    • affected 6aa58d8ad20a3323f42274c25820a6f54192422d – < 04226d8e3c4028dc451e9d8777356ec0f7919253
    • affected 6aa58d8ad20a3323f42274c25820a6f54192422d – < 9f0c4a46be1fe9b97dbe66d49204c1371e3ece65
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.23 – ≤ 6.6.*
    • unaffected 6.7.11 – ≤ 6.7.*
    • unaffected 6.8.2 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-26869 badge
[![CVE-2024-26869](https://cveledger.app/badge/CVE-2024-26869.svg)](https://cveledger.app/cve/CVE-2024-26869)

Record last updated .