linux-kernel - Re: Patch "smb3: when mounting with multichannel include it in requested capabilities" has been added to the 5.4-stable tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <YJjo/Jevkg9s7QkC@kroah.com>
Date:   Mon, 10 May 2021 10:04:12 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     linux-kernel@...r.kernel.org
Cc:     sprasad@...rosoft.com, stfrench@...rosoft.com, tom@...pey.com,
        stable-commits@...r.kernel.org
Subject: Re: Patch "smb3: when mounting with multichannel include it in
 requested capabilities" has been added to the 5.4-stable tree

On Mon, May 10, 2021 at 09:56:04AM +0200, gregkh@...uxfoundation.org wrote:
> 
> This is a note to let you know that I've just added the patch titled
> 
>     smb3: when mounting with multichannel include it in requested capabilities
> 
> to the 5.4-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> The filename of the patch is:
>      smb3-when-mounting-with-multichannel-include-it-in-requested-capabilities.patch
> and it can be found in the queue-5.4 subdirectory.
> 
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@...r.kernel.org> know about it.
> 
> 
> >From 679971e7213174efb56abc8fab1299d0a88db0e8 Mon Sep 17 00:00:00 2001
> From: Steve French <stfrench@...rosoft.com>
> Date: Fri, 7 May 2021 18:24:11 -0500
> Subject: smb3: when mounting with multichannel include it in requested capabilities
> 
> From: Steve French <stfrench@...rosoft.com>
> 
> commit 679971e7213174efb56abc8fab1299d0a88db0e8 upstream.
> 
> In the SMB3/SMB3.1.1 negotiate protocol request, we are supposed to
> advertise CAP_MULTICHANNEL capability when establishing multiple
> channels has been requested by the user doing the mount. See MS-SMB2
> sections 2.2.3 and 3.2.5.2
> 
> Without setting it there is some risk that multichannel could fail
> if the server interpreted the field strictly.
> 
> Reviewed-By: Tom Talpey <tom@...pey.com>
> Reviewed-by: Shyam Prasad N <sprasad@...rosoft.com>
> Cc: <stable@...r.kernel.org> # v5.8+
> Signed-off-by: Steve French <stfrench@...rosoft.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>

Oops, nope, dropped from 5.4.y, sorry for the noise.

greg k-h