From: Greg KH <gregkh@linuxfoundation.org>
To: Chanho Min <chanho.min@lge.com>
Cc: Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
linux-kernel@vger.kernel.org, gunho.lee@lge.com,
sashal@kernel.org
Subject: Re: [PATCH 0/4] smb: Backport UAF fixes for v5.4.y
Date: Sun, 24 Aug 2025 10:47:41 +0200 [thread overview]
Message-ID: <2025082410-finless-amused-5edc@gregkh> (raw)
In-Reply-To: <20250811094639.37446-1-chanho.min@lge.com>
On Mon, Aug 11, 2025 at 06:46:35PM +0900, Chanho Min wrote:
> This patch series backports four fixes from v5.10.y and later to the v5.4.y,
> addressing potential UAF issues in the SMB client implementation.
> The patches have been adapted to account for the directory rename from fs/smb/client/*
> to fs/cifs/* in v5.4.y, ensuring compatibility with the target kernel.
>
> Paulo Alcantara (4):
> smb: client: fix potential UAF in cifs_debug_files_proc_show()
> smb: client: fix potential UAF in is_valid_oplock_break()
> smb: client: fix potential UAF in smb2_is_valid_lease_break()
> smb: client: fix potential UAF in cifs_stats_proc_write()
>
> fs/cifs/cifs_debug.c | 4 ++++
> fs/cifs/cifsglob.h | 8 ++++++++
> fs/cifs/misc.c | 2 ++
> fs/cifs/smb2misc.c | 3 ++-
> 4 files changed, 16 insertions(+), 1 deletion(-)
>
We need these in newer kernels as well, otherwise you will have a
regression when moving to a new tree. Please resend patches for all of
the relevant trees and we will be glad to take them.
thanks,
greg k-h
prev parent reply other threads:[~2025-08-24 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 9:46 [PATCH 0/4] smb: Backport UAF fixes for v5.4.y Chanho Min
2025-08-11 9:46 ` [PATCH 1/4] smb: client: fix potential UAF in cifs_debug_files_proc_show() Chanho Min
2025-08-11 9:46 ` [PATCH 2/4] smb: client: fix potential UAF in is_valid_oplock_break() Chanho Min
2025-08-11 9:46 ` [PATCH 3/4] smb: client: fix potential UAF in smb2_is_valid_lease_break() Chanho Min
2025-08-11 9:46 ` [PATCH 4/4] smb: client: fix potential UAF in cifs_stats_proc_write() Chanho Min
2025-08-24 8:47 ` 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=2025082410-finless-amused-5edc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chanho.min@lge.com \
--cc=gunho.lee@lge.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=sashal@kernel.org \
--cc=sfrench@samba.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