From: Chao Yu <chao@kernel.org>
To: George Saad <geoo115@gmail.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: chao@kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
stable@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: fix use-after-free of sbi in f2fs_compress_write_end_io()
Date: Mon, 23 Mar 2026 19:06:25 +0800 [thread overview]
Message-ID: <ead2d70c-e7fc-479e-876f-3a28d5c03219@kernel.org> (raw)
In-Reply-To: <20260323104425.780693-1-geoo115@gmail.com>
On 3/23/26 18:44, George Saad wrote:
> In f2fs_compress_write_end_io(), dec_page_count(sbi, type) at line 1492
> can bring the F2FS_WB_CP_DATA counter to zero, unblocking
> f2fs_wait_on_all_pages() in f2fs_put_super() on a concurrent unmount
> CPU. The unmount path then proceeds to call
> f2fs_destroy_page_array_cache(sbi) and kfree(sbi). Meanwhile, the bio
> completion callback is still executing: when it reaches
> page_array_free(sbi, ...), it dereferences sbi->page_array_slab_size
> and sbi->page_array_slab within the now-freed f2fs_sb_info structure.
>
> This is the same class of bug as CVE-2026-23234 (which fixed the
> equivalent race in f2fs_write_end_io() in data.c), but in the
> compressed writeback completion path that was not covered by that fix.
>
> Fix this by caching sbi->page_array_slab and sbi->page_array_slab_size
> into local variables at function entry, before dec_page_count(). At
> function entry, sbi is guaranteed valid because the F2FS_WB_CP_DATA
> counter is still nonzero (this invocation has not yet decremented it),
> preventing the unmount path from proceeding past
> f2fs_wait_on_all_pages(). The cached values are then used in place of
> the post-decrement sbi dereference.
>
> Fixes: 4c8ff7095bef ("f2fs: support data compression")
> Cc: stable@vger.kernel.org
> Signed-off-by: George Saad <geoo115@gmail.com>
> ---
> Changes in v3:
> - Add Cc: stable@vger.kernel.org for backport to affected stable kernels
>
> Changes in v2:
> - Fix Fixes: tag commit hash (4c8ff7095bef, verified in Linus's tree)
>
> fs/f2fs/compress.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/compress.c b/fs/f2fs/compress.c
> index 7b68bf229..c3d837df3 100644
> --- a/fs/f2fs/compress.c
> +++ b/fs/f2fs/compress.c
> @@ -1479,11 +1479,20 @@ void f2fs_compress_write_end_io(struct bio *bio, struct folio *folio)
> {
> struct page *page = &folio->page;
> struct f2fs_sb_info *sbi = bio->bi_private;
> + struct kmem_cache *pa_slab = sbi->page_array_slab;
> + unsigned int pa_slab_size = sbi->page_array_slab_size;
> struct compress_io_ctx *cic = folio->private;
> enum count_type type = WB_DATA_TYPE(folio,
> f2fs_is_compressed_page(folio));
> int i;
>
> + /*
> + * Cache sbi fields before dec_page_count(), which may unblock
> + * f2fs_wait_on_all_pages() in the unmount path, allowing
> + * f2fs_put_super() to free sbi. At this point sbi is still
> + * valid because the F2FS_WB_CP_DATA counter is nonzero.
> + */
> +
> if (unlikely(bio->bi_status != BLK_STS_OK))
> mapping_set_error(cic->inode->i_mapping, -EIO);
>
> @@ -1500,7 +1509,10 @@ void f2fs_compress_write_end_io(struct bio *bio, struct folio *folio)
> end_page_writeback(cic->rpages[i]);
> }
>
> - page_array_free(sbi, cic->rpages, cic->nr_rpages);
> + if (likely(sizeof(struct page *) * cic->nr_rpages <= pa_slab_size))
> + kmem_cache_free(pa_slab, cic->rpages);
After sbi is freed, sbi->page_array_slab should be destroyed as well, so
pa_slab points to a freed memory, right?
Thanks,
> + else
> + kfree(cic->rpages);
> kmem_cache_free(cic_entry_slab, cic);
> }
>
next prev parent reply other threads:[~2026-03-23 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026032354-country-saddlebag-5331@gregkh>
2026-03-23 10:44 ` [PATCH v3] f2fs: fix use-after-free of sbi in f2fs_compress_write_end_io() George Saad
2026-03-23 11:06 ` Chao Yu [this message]
2026-03-23 11:21 ` [PATCH v4] " George Saad
2026-03-23 11:30 ` Chao Yu
2026-03-24 17:32 ` [f2fs-dev] " patchwork-bot+f2fs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ead2d70c-e7fc-479e-876f-3a28d5c03219@kernel.org \
--to=chao@kernel.org \
--cc=geoo115@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox