In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
Inthe Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel,the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fixtodo sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fixtodo sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fixtodo sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs:fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linuxkernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so thattheremaybe valid blkaddr in its direct node, once f2fs triggers background GCtomigrate the block,it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode duringGC,so that, it can forbid migrating inline_datainode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
IntheLinux kernel, thefollowing vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug asbelow:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybevalidblkaddr in its direct node, once f2fs triggers background GCto migrate theblock, it will hitf2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that,it can forbid migrating inline_data inode'sdata block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In theLinux kernel, the following vulnerability has been resolved:f2fs: fixto do sanitycheck on F2FS_INLINE_DATA flag ininode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The rootcause is: inline_datainode can be fuzzed, so thatthere maybevalid blkaddr in its directnode, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() duringdirty pagewriteback.Let's add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbidmigrating inline_data inode's data block forfixing.The Linux kernel CVE team has assigned CVE-2024-44942 to this issue.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
Inthe Linuxkernel, the following vulnerability has been resolved:f2fs: fix to dosanity checkon F2FS_INLINE_DATA flag in inodeduring GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm:kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root causeis: inline_data inodecan be fuzzed, so that theremaybe validblkaddr in its direct node,once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirtypagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migratinginline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let sadd sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode sdata block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Lets add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inodes data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports af2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let sadd sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode sdata block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reportsa f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU:1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Lets add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inodes data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
Inthe Linux kernel,the following vulnerabilityhas been resolved:f2fs:fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fsbug as below:------------[cut here ]------------kernelBUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inodecan be fuzzed, so that there maybe valid blkaddr inits direct node, once f2fs triggers background GCto migrate the block, it willhit f2fs_bug_on() during dirty pagewriteback.Let sadd sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, itcan forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
IntheLinux kernel, thefollowing vulnerability hasbeen resolved:f2fs: fixto do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bugas below:------------[ cuthere ]------------kernel BUGat fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Nottainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode canbe fuzzed, so that there maybe valid blkaddr in itsdirect node, once f2fs triggers background GCto migrate the block, it will hitf2fs_bug_on() during dirty pagewriteback.Let s addsanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it canforbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
| linux | | https://git.kernel.org/linus/fc01008c92f40015aeeced94750855a7111b6929 | https://git.kernel.org/linus/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to do sanity check on F2FS_INLINE_DATA flag in inode during GCsyzbot reports a f2fs bug as below:------------[ cut here ]------------kernel BUG at fs/f2fs/inline.c:258!CPU: 1 PID: 34 Comm: kworker/u8:2 Not tainted 6.9.0-rc6-syzkaller-00012-g9e4bc4bcae01 #0RIP: 0010:f2fs_write_inline_data+0x781/0x790 fs/f2fs/inline.c:258Call Trace: f2fs_write_single_data_page+0xb65/0x1d60 fs/f2fs/data.c:2834 f2fs_write_cache_pages fs/f2fs/data.c:3133 [inline] __f2fs_write_data_pages fs/f2fs/data.c:3288 [inline] f2fs_write_data_pages+0x1efe/0x3a90 fs/f2fs/data.c:3315 do_writepages+0x35b/0x870 mm/page-writeback.c:2612 __writeback_single_inode+0x165/0x10b0 fs/fs-writeback.c:1650 writeback_sb_inodes+0x905/0x1260 fs/fs-writeback.c:1941 wb_writeback+0x457/0xce0 fs/fs-writeback.c:2117 wb_do_writeback fs/fs-writeback.c:2264 [inline] wb_workfn+0x410/0x1090 fs/fs-writeback.c:2304 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0xa12/0x17c0 kernel/workqueue.c:3335 worker_thread+0x86d/0xd70 kernel/workqueue.c:3416 kthread+0x2f2/0x390 kernel/kthread.c:388 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244The root cause is: inline_data inode can be fuzzed, so that there maybe valid blkaddr in its direct node, once f2fs triggers background GCto migrate the block, it will hit f2fs_bug_on() during dirty pagewriteback.Let s add sanity check on F2FS_INLINE_DATA flag in inode during GC,so that, it can forbid migrating inline_data inode s data block forfixing.
