From: Greg KH <gregkh@linuxfoundation.org>
To: Jiucheng Xu <Jiucheng.Xu@amlogic.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Tuan Zhang <Tuan.Zhang@amlogic.com>,
Jianxin Pan <Jianxin.Pan@amlogic.com>
Subject: Re: f2fs: fix to avoid UAF in f2fs_sync_inode_meta()
Date: Mon, 18 Aug 2025 12:03:31 +0200 [thread overview]
Message-ID: <2025081817-python-habitant-17e3@gregkh> (raw)
In-Reply-To: <ae6791c0-8bd0-4388-bb65-53c421b35380@amlogic.com>
On Mon, Aug 18, 2025 at 09:46:32AM +0000, Jiucheng Xu wrote:
> Dear 5.15.y maintainers,
>
> A f2fs patch should be backported from upstream mainline to the stable
> 5.15.y branch. The patch's information is shown as below:
>
> [Subject]
> f2fs: fix to avoid UAF in f2fs_sync_inode_meta()
>
> [Upstream commit ID]
> 7c30d79930132466f5be7d0b57add14d1a016bda
>
> [Kernel version]
> 5.15.y
>
> [Why]
> This patch fixes the issue where the f2fs_inode_info.gdirty_list is not
> deleted when evicting the inode. This would cause the gdirty_list to
> remain incorrectly linked when the f2fs_inode_info is reallocated, which
> in turn would be detected by __list_del_entry_valid during list_del_init.
>
> On the Android 5.15 U arm platform, the issue that could be reproduced
> within 24 hours has not recurred for a week after applying this patch.
It's already queued up for the next 5.15.y release, thanks!
greg k-h
prev parent reply other threads:[~2025-08-18 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 9:46 f2fs: fix to avoid UAF in f2fs_sync_inode_meta() Jiucheng Xu
2025-08-18 10:03 ` 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=2025081817-python-habitant-17e3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Jianxin.Pan@amlogic.com \
--cc=Jiucheng.Xu@amlogic.com \
--cc=Tuan.Zhang@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