CVE-2024-26869 json
f2fs: fix to truncate meta inode pages forcely
published 2024-04-17 2 y ago modified 2026-10-30 10 d ago also EUVD-2024-24131
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.23, 6.7.11, 6.8.2, 6.9
- linux Debian 14, Debian 13 6.7.12-1
debian advisories DEBIAN-CVE-2024-26869
- linux Ubuntu 24.04 LTS 6.8.0-35.35
- linux-aws Ubuntu 24.04 LTS 6.8.0-1009.9
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1008.9
- linux-gke Ubuntu 24.04 LTS 6.8.0-1004.7
- linux-ibm Ubuntu 24.04 LTS 6.8.0-1006.6
- linux-azure Ubuntu 24.04 LTS 6.8.0-1008.8
- linux-raspi Ubuntu 24.04 LTS 6.8.0-1005.5
- linux-riscv Ubuntu 24.04 LTS 6.8.0-35.35.1
ubuntu advisories UBUNTU-CVE-2024-26869
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/0721a4f85d12a364002a9476c84b930fbc993f83 commit
- git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694 commit
- git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189 commit
- git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253 commit
- git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-26869 updated cvss 4.7
kernel: f2fs: fix to truncate meta inode pages forcely
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
- Technology feeds
References
- git.kernel.org /stable/c/0721a4f85d12a364002a9476c84b930fbc993f83
-
git.kernel.org
/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694
patch
-
git.kernel.org
/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189
patch
-
git.kernel.org
/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253
patch
-
git.kernel.org
/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65
patch
Sources
- CVE List CVE-2024-26869
- NVD CVE-2024-26869
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.