High 7.8Published Mar 4, 2026

CVE-2026-23234f2fs: fix to avoid UAF in f2fs_write_end_io()

Updated under an hour ago (Oct 28, 2026, 1:50 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: May 11, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from e234088758fca3a669ebb1a02d8bf7bf60f0e4ff before 0fb58aff0dafd6837cc91f4154f3ed6e020358fa; from e234088758fca3a669ebb1a02d8bf7bf60f0e4ff before 2f67ff1e15a8a4d0e4ffc6564ab20d03d7398fe9; from e234088758fca3a669ebb1a02d8bf7bf60f0e4ff before 505e1c0530db6152cab3feef8e3e4da3d3e358c9; from e234088758fca3a669ebb1a02d8bf7bf60f0e4ff before acc2c97fc0005846e5cf11b5ba3189fef130c9b3; from e234088758fca3a669ebb1a02d8bf7bf60f0e4ff before cf4a9e1bc8129eb63fda5f8bdcd8d87f0bd76f42; from e234088758fca3a669ebb1a02d8bf7bf60f0e4ff before 995030be4ce6338c6ff814583c14166446a64008; from e234088758fca3a669ebb1a02d8bf7bf60f0e4ff before a42f99be8a16b32a0bb91bb6dda212a6ad61be5d; from e234088758fca3a669ebb1a02d8bf7bf60f0e4ff before ce2739e482bce8d2c014d76c4531c877f382aa54	CNA record
linux linux_kernel linux:linux_kernel	from 3.13 before 5.10.251; from 5.11 before 5.15.201; from 5.16 before 6.1.164; from 6.2 before 6.6.127; from 6.7 before 6.12.74; from 6.13 before 6.18.13; from 6.19 before 6.19.3	NVD

References

References

https://git.kernel.org/stable/c/0fb58aff0dafd6837cc91f4154f3ed6e020358fa	patch
https://git.kernel.org/stable/c/2f67ff1e15a8a4d0e4ffc6564ab20d03d7398fe9	patch
https://git.kernel.org/stable/c/505e1c0530db6152cab3feef8e3e4da3d3e358c9	patch
https://git.kernel.org/stable/c/acc2c97fc0005846e5cf11b5ba3189fef130c9b3	patch
https://git.kernel.org/stable/c/cf4a9e1bc8129eb63fda5f8bdcd8d87f0bd76f42	patch
https://git.kernel.org/stable/c/995030be4ce6338c6ff814583c14166446a64008	patch
https://git.kernel.org/stable/c/a42f99be8a16b32a0bb91bb6dda212a6ad61be5d	patch
https://git.kernel.org/stable/c/ce2739e482bce8d2c014d76c4531c877f382aa54	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.