Answer in brief
CVE-2024-42273 records a High severity (CVSS 7.8) vulnerability in f2fs: assign CURSEG_ALL_DATA_ATGC if blkaddr is valid. 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.
CVSS is 7.8. 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 | >=7c972c89457511007dfc933814c06786905e515c <5fd057160ab240dd816ae09b625395d54c297de1 || >=417b8a91f4e8831cadaf85c3f15c6991c1f54dde <4239571c5db46a42f723b8fa8394039187c34439 || >=4961acdd65c956e97c1a000c82d91a8c1cdbe44b <0cd106612396656d6f1ca17ef192c6759bb60791 || >=4961acdd65c956e97c1a000c82d91a8c1cdbe44b <8cb1f4080dd91c6e6b01dbea013a3f42341cb6a1 || 7ea0f29d9fd84905051be020c0df7d557e286136 || b8094c0f1aae329b1c60a275a780d6c2c9ff7aa3 || >=6.1.77 <6.1.104 || >=6.6.16 <6.6.45 || >=5.15.149 <5.16 || >=6.7.4 <6.8 | 5fd057160ab240dd816ae09b625395d54c297de1, 4239571c5db46a42f723b8fa8394039187c34439, 0cd106612396656d6f1ca17ef192c6759bb60791, 8cb1f4080dd91c6e6b01dbea013a3f42341cb6a1, 6.1.104, 6.6.45, 5.16, 6.8 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Aug 17, 2024
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: assign CURSEG_ALL_DATA_ATGC if blkaddr is valid mkdir /mnt/test/comp f2fs_io setflags compression /mnt/test/comp dd if=/dev/zero of=/mnt/test/comp/testfile bs=16k count=1 truncate --size 13 /mnt/test/comp/testfile In the above scenario, we can get a BUG_ON. kernel BUG at fs/f2fs/segment.c:3589! Call Trace: do_write_page+0x78/0x390 [f2fs] f2fs_outplace_write_data+0x62/0xb0 [f2fs] f2fs_do_write_data_page+0x275/0x740 [f2fs] f2fs_write_single_data_page+0x1dc/0x8f0 [f2fs] f2fs_write_multi_pages+0x1e5/0xae0 [f2fs] f2fs_write_cache_pages+0xab1/0xc60 [f2fs] f2fs_write_data_pages+0x2d8/0x330 [f2fs] do_writepages+0xcf/0x270 __writeback_single_inode+0x44/0x350 writeback_sb_inodes+0x242/0x530 __writeback_inodes_wb+0x54/0xf0 wb_writeback+0x192/0x310 wb_workfn+0x30d/0x400 The reason is we gave CURSEG_ALL_DATA_ATGC to COMPR_ADDR where the page was set the gcing flag by set_cluster_dirty().
Quoted source text, attributed separately from HOL analysis.