From: Greg KH <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: manizada <manizada@pm.me>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Please apply 3da1fdf4efbc to stable
Date: Wed, 27 May 2026 14:16:39 +0200 [thread overview]
Message-ID: <2026052725-stir-yearbook-e753@gregkh> (raw)
In-Reply-To: <ahbeRcvu5qN55gaE@eldamar.lan>
On Wed, May 27, 2026 at 02:06:29PM +0200, Salvatore Bonaccorso wrote:
> Hi Greg,
>
> Not Asmin here, but saw the following.
>
> On Wed, May 27, 2026 at 10:08:03AM +0200, Greg KH wrote:
> > On Tue, May 26, 2026 at 05:08:43PM +0000, manizada wrote:
> > > Hi stable team,
> > >
> > > Please apply the following upstream commit to the supported stable trees:
> > >
> > > 3da1fdf4efbc490041eb4f836bf596201203f8f2
> > > smb: client: reject userspace cifs.spnego descriptions
> > >
> > > Reason:
> > > cifs.spnego descriptions contain authority-bearing fields consumed by
> > > cifs.upcall. This commit prevents userspace from creating trusted
> > > cifs.spnego descriptions via request_key(2)/add_key(2).
> > >
> > > Requested branches:
> > > Please apply to all currently supported stable/LTS branches where it is
> > > applicable, including 7.0.y, 6.18.y, 6.12.y, 6.6.y, 6.1.y, 5.15.y, and
> > > 5.10.y.
> >
> > This does not apply to the 5.15.y or 5.10.y tree, please provide a
> > backported version that can apply there.
>
> There was 38c8a9a52082 ("smb: move client and server files to common
> directory fs/smb") moving the files around (and which got as well
> backported to the 6.1.y series). So the following should do the trick.
That worked, thanks!
greg k-h
prev parent reply other threads:[~2026-05-27 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 17:08 Please apply 3da1fdf4efbc to stable manizada
2026-05-27 8:08 ` Greg KH
2026-05-27 12:06 ` Salvatore Bonaccorso
2026-05-27 12:16 ` 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=2026052725-stir-yearbook-e753@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=carnil@debian.org \
--cc=manizada@pm.me \
--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