Vulnerability · Published Jul 4, 2025 · Assigned by Linux

CVE-2025-38218f2fs: fix to do sanity check on sit_bitmap_size

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.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 91.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on sit_bitmap_size w/ below testcase, resize will generate a corrupted image which contains inconsistent metadata, so when mounting such image, it will trigger kernel panic: touch img truncate -s $((512*1024*1024*1024)) img mkfs.f2fs -f img $((256*1024*1024)) resize.f2fs -s -i img -t $((1024*1024*1024)) mount img /mnt/f2fs ------------[ cut here ]------------ kernel BUG at fs/f2fs/segment.h:863! Oops: invalid opcode: 0000 [#1] SMP PTI CPU: 11 UID: 0 PID: 3922 Comm: mount Not tainted 6.15.0-rc1+ #191 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:f2fs_ra_meta_pages+0x47c/0x490 Call Trace: f2fs_build_segment_manager+0x11c3/0x2600 f2fs_fill_super+0xe97/0x2840 mount_bdev+0xf4/0x140 legacy_get_tree+0x2b/0x50 vfs_get_tree+0x29/0xd0 path_mount+0x487/0xaf0 __x64_sys_mount+0x116/0x150 do_syscall_64+0x82/0x190 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fdbfde1bcfe The reaseon is: sit_i->bitmap_size is 192, so size of sit bitmap is 192*8=1536, at maximum there are 1536 sit blocks, however MAIN_SEGS is 261893, so that sit_blk_cnt is 4762, build_sit_entries() -> current_sit_addr() tries to access out-of-boundary in sit_bitmap at offset from [1536, 4762), once sit_bitmap and sit_bitmap_mirror is not the same, it will trigger f2fs_bug_on(). Let's add sanity check in f2fs_sanity_check_ckpt() to avoid panic.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.147-1DEBIAN-CVE-2025-38218
Debian:13linux6.12.35-1DEBIAN-CVE-2025-38218
Debian:14linux6.12.35-1DEBIAN-CVE-2025-38218
Ubuntu:22.04:LTSlinux5.15.0-156.166UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux6.8.0-100.100UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-aws5.15.0-1092.99UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-aws6.8.0-1046.49UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-aws-6.146.14.0-1015.15~24.04.1UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-aws-6.146.14.0-1015.15~24.04.1USN-7833-3
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1046.49~22.04.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-azure5.15.0-1096.105UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-azure6.8.0-1046.52UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-azure-6.146.14.0-1014.14~24.04.1UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-azure-6.146.14.0-1014.14~24.04.1USN-7834-1
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1051.57~22.04.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1096.105.1UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1046.53UBUNTU-CVE-2025-38218
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1046.53~22.04.1UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-azure-nvidia-6.146.14.0-1007.7UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-azure-nvidia-6.146.14.0-1007.7USN-7834-1
Ubuntu:22.04:LTSlinux-gcp5.15.0-1092.101UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-gcp6.8.0-1047.50UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-gcp-6.146.14.0-1018.19~24.04.1UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-gcp-6.146.14.0-1018.19~24.04.1USN-7833-4
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1047.50~22.04.2UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-gke5.15.0-1089.95UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-gke6.8.0-1043.48UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1075.83UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1030.33UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-hwe-6.146.14.0-34.34~24.04.1USN-7856-1
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-100.100~22.04.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-ibm5.15.0-1086.89UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-ibm6.8.0-1044.44UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1044.44~22.04.1UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1087.93UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-kvm5.15.0-1088.93UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-156.166UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-100.100.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-100.100.1~22.04.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1087.88UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1046.49UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1046.49~22.04.1UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1046.49.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1045.45UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1020.20UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1034.34UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-oem-6.146.14.0-1014.14USN-7833-1
Ubuntu:24.04:LTSlinux-oem-6.146.14.0-1014.14UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-oracle5.15.0-1090.96UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-oracle6.8.0-1043.44UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-oracle-6.146.14.0-1015.15~24.04.1USN-7833-1
Ubuntu:24.04:LTSlinux-oracle-6.146.14.0-1015.15~24.04.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1043.44~22.04.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-raspi5.15.0-1086.89UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-raspi6.8.0-1047.51UBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-riscv-6.146.14.0-34.34.1~24.04.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-100.100~22.04.1UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-38218
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1023.24UBUNTU-CVE-2025-38218
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1056.60UBUNTU-CVE-2025-38218

Affected products (as reported)

VendorProductVersions
Linux Linux 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – before 82f51bff393e4c12cf4de553120ca831cfa4ef1998e4da8ca301e062d79ae168c67e56f3c3de3ce4 – before 38ef48a8afef8df646b6f6ae7abb872f18b533c198e4da8ca301e062d79ae168c67e56f3c3de3ce4 – before ad862f71016ba38039df1c96ed55c0a4314cc18398e4da8ca301e062d79ae168c67e56f3c3de3ce4 – before 79ef8a6c4ec53d327580fd7d2b522cf4f1d05b0c98e4da8ca301e062d79ae168c67e56f3c3de3ce4 – before ee1b421c469876544e297ec1090574bd7610024798e4da8ca301e062d79ae168c67e56f3c3de3ce4 – before 3e5ac62a56a24f4d88ce8ffd7bc452428b23586898e4da8ca301e062d79ae168c67e56f3c3de3ce4 – before 5db0d252c64e91ba1929c70112352e85dc5751e7
Linux Linux 3.8

References