From: Greg KH <gregkh@linuxfoundation.org>
To: Jiucheng Xu <jiucheng.xu@amlogic.com>
Cc: stable@vger.kernel.org
Subject: Re: f2fs: fix UAF issue in f2fs_merge_page_bio()
Date: Mon, 6 Jul 2026 14:08:57 +0200 [thread overview]
Message-ID: <2026070631-vaporizer-viability-d57f@gregkh> (raw)
In-Reply-To: <e6003504-96f1-4dc8-9e6b-e17c8f809d75@amlogic.com>
On Mon, Jul 06, 2026 at 04:52:12PM +0800, Jiucheng Xu wrote:
> Dear maintainers,
>
> A f2fs patch should be backported from upstream mainline to the stable
> 5.15.y branches. The patch's information is shown as below:
>
> [Subject]
> f2fs: fix UAF issue in f2fs_merge_page_bio()
>
> [Upstream commit ID]
> edf7e9040fc52c922db947f9c6c36f07377c52ea
>
> [Kernel version]
> 5.15.y
>
> [Why]
> We encountered the same issue on the 5.15 kernel version. After referring to
> the modifications in the upstream, the issue was solved.
Great, please provide a working backport that you have tested for this
branch, and all of the newer stable branches, and we will be glad to
apply it. As-is, it does not apply at all.
thanks,
greg k-h
prev parent reply other threads:[~2026-07-06 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 8:52 f2fs: fix UAF issue in f2fs_merge_page_bio() Jiucheng Xu
2026-07-06 12:08 ` Greg KH [this message]
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=2026070631-vaporizer-viability-d57f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jiucheng.xu@amlogic.com \
--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