Answer in brief
CVE-2024-42296 records a High severity (CVSS 7.8) vulnerability in f2fs: fix return value of f2fs_convert_inline_inode(). 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 | >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <70f5ef5f33c333cfb286116fa3af74ac9bc84f1b || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <47a8ddcdcaccd9b891db4574795e46a33a121ac2 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <077f0e24b27c4b44841593c7edbd1993be9eecb5 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <1e7725814361c8c008d131db195cef8274ff26b8 || >=98e4da8ca301e062d79ae168c67e56f3c3de3ce4 <a8eb3de28e7a365690c61161e7a07a4fc7c60bbf | 70f5ef5f33c333cfb286116fa3af74ac9bc84f1b, 47a8ddcdcaccd9b891db4574795e46a33a121ac2, 077f0e24b27c4b44841593c7edbd1993be9eecb5, 1e7725814361c8c008d131db195cef8274ff26b8, a8eb3de28e7a365690c61161e7a07a4fc7c60bbf |
| Linux/Linuxgeneric | 3.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: fix return value of f2fs_convert_inline_inode() If device is readonly, make f2fs_convert_inline_inode() return EROFS instead of zero, otherwise it may trigger panic during writeback of inline inode's dirty page as below: f2fs_write_single_data_page+0xbb6/0x1e90 fs/f2fs/data.c:2888 f2fs_write_cache_pages fs/f2fs/data.c:3187 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3342 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3369 do_writepages+0x359/0x870 mm/page-writeback.c:2634 filemap_fdatawrite_wbc+0x125/0x180 mm/filemap.c:397 __filemap_fdatawrite_range mm/filemap.c:430 [inline] file_write_and_wait_range+0x1aa/0x290 mm/filemap.c:788 f2fs_do_sync_file+0x68a/0x1ae0 fs/f2fs/file.c:276 generic_write_sync include/linux/fs.h:2806 [inline] f2fs_file_write_iter+0x7bd/0x24e0 fs/f2fs/file.c:4977 call_write_iter include/linux/fs.h:2114 [inline] new_sync_write fs/read_write.c:497 [inline] vfs_write+0xa72/0xc90 fs/read_write.c:590 ksys_write+0x1a0/0x2c0 fs/read_write.c:643 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f
Quoted source text, attributed separately from HOL analysis.