f2fs: fix to avoid UAF in f2fs_write_end_io()

Summary

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid UAF in f2fs_write_end_io() As syzbot reported an use-after-free issue in f2fs_write_end_io(). It is caused by below race condition: loop device umount • worker_thread • loop_process_work • do_req_filebacked • lo_rw_aio • lo_rw_aio_complete • blk_mq_end_request • blk_update_request • f2fs_write_end_io • dec_page_count • folio_end_writeback • kill_f2fs_super • kill_block_super • f2fs_put_super : free(sbi) : get_pages(, F2FS_WB_CP_DATA) accessed sbi which is freed In kill_f2fs_super(), we will drop all page caches of f2fs inodes before call free(sbi), it guarantee that all folios should end its writeback, so it should be safe to access sbi before last folio_end_writeback(). Let's relocate ckpt thread wakeup flow before folio_end_writeback() to resolve this issue.

Timeline

1. Mar 4, 2026, 2:36 PM UTCCVE published
2. May 11, 2026, 10:02 PM UTCRecord last updated

Affected versions

• Linux Linux

  Version range not reported

• Linux Linux

  3.13

References 8