From: Sasha Levin <sashal@kernel.org>
To: Robert Garcia <rob_garcia@163.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, linux-cifs@vger.kernel.org,
Steve French <smfrench@gmail.com>,
Paulo Alcantara <pc@manguebit.org>
Subject: Re: [PATCH 5.15.y] smb: client: fix potential UAF in smb2_is_valid_oplock_break()
Date: Mon, 20 Apr 2026 09:21:12 -0400 [thread overview]
Message-ID: <20260420-stable-reply-smb-oplock-5-15@kernel.org> (raw)
In-Reply-To: <20260417063426.1101332-1-rob_garcia@163.com>
On Fri, Apr 17, 2026, Robert Garcia wrote:
> Backport of 22863485a462 ("smb: client: fix potential UAF in
> smb2_is_valid_oplock_break()") to 5.15.y.
Queued for 5.15, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-04-20 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 6:34 [PATCH 5.15.y] smb: client: fix potential UAF in smb2_is_valid_oplock_break() Robert Garcia
2026-04-20 13:21 ` Sasha Levin [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=20260420-stable-reply-smb-oplock-5-15@kernel.org \
--to=sashal@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=rob_garcia@163.com \
--cc=smfrench@gmail.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