Answer in brief
CVE-2025-38218 records a Unknown severity vulnerability in f2fs: fix to do sanity check on sit_bitmap_size. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38218 records a Unknown severity vulnerability in f2fs: fix to do sanity check on sit_bitmap_size. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <82f51bff393e4c12cf4de553120ca831cfa4ef19 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <38ef48a8afef8df646b6f6ae7abb872f18b533c1 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ad862f71016ba38039df1c96ed55c0a4314cc183 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <79ef8a6c4ec53d327580fd7d2b522cf4f1d05b0c || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ee1b421c469876544e297ec1090574bd76100247 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <3e5ac62a56a24f4d88ce8ffd7bc452428b235868 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <5db0d252c64e91ba1929c70112352e85dc5751e7 | 82f51bff393e4c12cf4de553120ca831cfa4ef19, 38ef48a8afef8df646b6f6ae7abb872f18b533c1, ad862f71016ba38039df1c96ed55c0a4314cc183, 79ef8a6c4ec53d327580fd7d2b522cf4f1d05b0c, ee1b421c469876544e297ec1090574bd76100247, 3e5ac62a56a24f4d88ce8ffd7bc452428b235868, 5db0d252c64e91ba1929c70112352e85dc5751e7 |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Jul 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <82f51bff393e4c12cf4de553120ca831cfa4ef19 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <38ef48a8afef8df646b6f6ae7abb872f18b533c1 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ad862f71016ba38039df1c96ed55c0a4314cc183 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <79ef8a6c4ec53d327580fd7d2b522cf4f1d05b0c || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <ee1b421c469876544e297ec1090574bd76100247 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <3e5ac62a56a24f4d88ce8ffd7bc452428b235868 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <5db0d252c64e91ba1929c70112352e85dc5751e7 | 82f51bff393e4c12cf4de553120ca831cfa4ef19, 38ef48a8afef8df646b6f6ae7abb872f18b533c1, ad862f71016ba38039df1c96ed55c0a4314cc183, 79ef8a6c4ec53d327580fd7d2b522cf4f1d05b0c, ee1b421c469876544e297ec1090574bd76100247, 3e5ac62a56a24f4d88ce8ffd7bc452428b235868, 5db0d252c64e91ba1929c70112352e85dc5751e7 |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Jul 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.