Vulnerability · Published Apr 17, 2024 · Assigned by Linux
CVE-2024-26869f2fs: fix to truncate meta inode pages forcely
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | no fix listed | DEBIAN-CVE-2024-26869 |
| Debian:13 | linux | 6.7.12-1 | DEBIAN-CVE-2024-26869 |
| Debian:14 | linux | 6.7.12-1 | DEBIAN-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux | 6.8.0-35.35 | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux | 6.8.0-35.35 | USN-6816-1 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1009.9 | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1009.9 | USN-6817-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1008.8 | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1008.8 | USN-6817-3 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1008.9 | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1008.9 | USN-6817-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1004.7 | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1004.7 | USN-6817-3 |
| Ubuntu:22.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1006.6 | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1006.6 | USN-6816-1 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-intel-iotg | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-kvm | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-35.35.1 | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-35.35.1 | USN-6816-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1006.6 | USN-6817-2 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1006.6 | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1006.6 | USN-6878-1 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1006.6 | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1005.5 | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1005.5 | USN-6816-1 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:24.04:LTS | linux-riscv | 6.8.0-35.35.1 | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-26869 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | no fix listed | UBUNTU-CVE-2024-26869 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 6aa58d8ad20a3323f42274c25820a6f54192422d – before 0721a4f85d12a364002a9476c84b930fbc993f836aa58d8ad20a3323f42274c25820a6f54192422d – before c92f2927df860a60ba815d3ee610a944b92a86946aa58d8ad20a3323f42274c25820a6f54192422d – before 77bfdb89cc222fc7bfe198eda77bdc427d5ac1896aa58d8ad20a3323f42274c25820a6f54192422d – before 04226d8e3c4028dc451e9d8777356ec0f79192536aa58d8ad20a3323f42274c25820a6f54192422d – before 9f0c4a46be1fe9b97dbe66d49204c1371e3ece65 |
| Linux | Linux | 4.19 |
References
- https://git.kernel.org/stable/c/0721a4f85d12a364002a9476c84b930fbc993f83
- https://git.kernel.org/stable/c/c92f2927df860a60ba815d3ee610a944b92a8694
- https://git.kernel.org/stable/c/77bfdb89cc222fc7bfe198eda77bdc427d5ac189
- https://git.kernel.org/stable/c/04226d8e3c4028dc451e9d8777356ec0f7919253
- https://git.kernel.org/stable/c/9f0c4a46be1fe9b97dbe66d49204c1371e3ece65