{"vulnerability": "CVE-2024-44942", "sightings": [{"uuid": "b3935449-103d-45c8-8553-7ee7043ce583", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-44942", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "b9b71aac-e5ec-4815-9be5-8ca2e04c00e9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-44942", "type": "seen", "source": "https://t.me/cvedetector/4131", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44942 - \"F2FS Linux Kernel BUG in f2fs_write_inline_data\"\", \n  \"Content\": \"CVE ID : CVE-2024-44942 \nPublished : Aug. 26, 2024, 12:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nf2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GC  \n  \nsyzbot reports a f2fs bug as below:  \n  \n------------[ cut here ]------------  \nkernel BUG at fs/f2fs/inline.c:258!  \nCPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0  \nRIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258  \nCall Trace:  \n f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834  \n f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline]  \n __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline]  \n f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315  \n do_writepages+0x35b/0x870 mm/page-writeback.c:2612  \n __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650  \n writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941  \n wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117  \n wb_do_writeback fs/fs-writeback.c:2264 [inline]  \n wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304  \n process_one_work kernel/workqueue.c:3254 [inline]  \n process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335  \n worker_thread+0x86d/0xd70 kernel/workqueue.c:3416  \n kthread+0x2f2/0x390 kernel/kthread.c:388  \n ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147  \n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244  \n  \nThe root cause is: inline_data inode can be fuzzed, so that there may  \nbe valid blkaddr in its direct node, once f2fs triggers background GC  \nto migrate the block, it will hit f2fs_bug_on() during dirty page  \nwriteback.  \n  \nLet's add sanity check on F2FS_INLINE_DATA flag in inode during GC,  \nso that, it can forbid migrating inline_data inode's data block for  \nfixing. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"26 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-26T15:23:49.000000Z"}]}