f2fs: fix to avoid UAF in f2fs_write_end_io()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e234088758fca3a669ebb1a02d8bf7bf60f0e4ff · < 995030be4ce6338c6ff814583c14166446a64008| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
A race in the Linux kernel’s f2fs_write_end_io() can access freed filesystem state. It occurs when loop-device write completion overlaps with an f2fs unmount. The input does not establish whether an attacker can trigger the race, or what access or interaction would be required.
Engineers running Linux kernels with f2fs should check their kernel versions against the vendor advisory; affected versions are not specified here.