CVE-2023-53537

f2fs: fix to avoid use-after-free for cached IPU bio

HIGH
7.8
CVSS Score
Published: October 4, 2025 at 03:16 PM UTC
Updated: August 5, 2026 at 10:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use-after-free for cached IPU bio xfstest generic/019 reports a bug: kernel BUG at mm/filemap.c:1619! RIP: 0010:folio_end_writeback+0x8a/0x90 Call Trace: end_page_writeback+0x1c/0x60 f2fs_write_end_io+0x199/0x420 bio_endio+0x104/0x180 submit_bio_noacct+0xa5/0x510 submit_bio+0x48/0x80 f2fs_submit_write_bio+0x35/0x300 f2fs_submit_merged_ipu_write+0x2a0/0x2b0 f2fs_write_single_data_page+0x838/0x8b0 f2fs_write_cache_pages+0x379/0xa30 f2fs_write_data_pages+0x30c/0x340 do_writepages+0xd8/0x1b0 __writeback_single_inode+0x44/0x370 writeback_sb_inodes+0x233/0x4d0 __writeback_inodes_wb+0x56/0xf0 wb_writeback+0x1dd/0x2d0 wb_workfn+0x367/0x4a0 process_one_work+0x21d/0x430 worker_thread+0x4e/0x3c0 kthread+0x103/0x130 ret_from_fork+0x2c/0x50 The root cause is: after cp_error is set, f2fs_submit_merged_ipu_write() in f2fs_write_single_data_page() tries to flush IPU bio in cache, however f2fs_submit_merged_ipu_write() missed to check validity of @bio parameter, result in submitting random cached bio which belong to other IO context, then it will cause use-after-free issue, fix it by adding additional validity check.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.15.1115.16 ≤ v < 6.1.285.5 ≤ v < 5.10.1805.5 ≤ v < 5.15.1115.5 ≤ v < 6.1.285.5 ≤ v < 6.2.155.5 ≤ v < 6.3.25.5 ≤ v < 6.46.2 ≤ v < 6.2.156.3 ≤ v < 6.3.20b20fcec8651569935a10afe03fedc0b812d044e5.5
Vendor states this is fixed in 5cdb422c839134273866208dad5360835ddb9794 (fixed)
Vendor states this is fixed in 7d058f0ab161437369ad6e45a4b67c2886e71373 (fixed)
Vendor states this is fixed in 97ec6f1788cc6bee3f8c89cb908e1a2a1cd859bb (fixed)
Vendor states this is fixed in 9a7f63283af6befc0f91d549f4f6917dff7479a9 (fixed)
Vendor states this is fixed in af4ce124d7bd74cb839bbdaccffbb416771a56b5 (fixed)
Vendor states this is fixed in b2f423fda64fb49213aa0ed5056079cf295a5df2 (fixed)
Vendor states this is fixed in 5.10.180 (unaffected)
Vendor states this is fixed in 5.15.111 (unaffected)
Vendor states this is fixed in 5.5 (unaffected)
Vendor states this is fixed in 6.1.28 (unaffected)
Vendor states this is fixed in 6.2.15 (unaffected)
Vendor states this is fixed in 6.3.2 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card