Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Birtwhistle, Daniel" <daniel.birtwhistle@gehealthcare.com>
Cc: Steve French <sfrench@samba.org>,
	Paulo Alcantara <pc@manguebit.org>,
	"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>,
	"security@kernel.org" <security@kernel.org>
Subject: Re: [BUG 1/3] smb: client: SMB2/3 signature failures are logged but the response is accepted
Date: Mon, 20 Jul 2026 08:13:11 +0200	[thread overview]
Message-ID: <2026072010-affront-blog-f082@gregkh> (raw)
In-Reply-To: <SN4PR22MB28883DAF57E0B4D4BFB1C22AEEC42@SN4PR22MB2888.namprd22.prod.outlook.com>

On Sun, Jul 19, 2026 at 06:05:01PM +0000, Birtwhistle, Daniel wrote:
> Hello Steve, Paulo, and linux-cifs maintainers,
> 
> My name is Daniel Birtwhistle. In my role, I assess security properties of
> software inherited by GE HealthCare products. I am writing personally as the
> researcher and technical contact.
> 
> This is the first of three coordinated CIFS client reports. This message covers
> response-signature enforcement. The companions cover server-provided symlinks
> escaping mount confinement and client-required sealing being dropped after
> reconnect; all three defects have different fixes and can be classified
> independently.

As you sent these to a public list, no need to get security@kernel.org
involved.

Also:

> I have the minimal candidate patch, source harness, raw transcript, trace
> results and matched controls. I have not posted or attached the reproducer,
> but can provide it directly for review and can test a maintainer-proposed fix.

Always send patches, as the documentation asks, so you can get full
credit for resolving the issue if the fix is correct.

Same for the other 2 emails you sent.

thanks,

greg k-h

  parent reply	other threads:[~2026-07-20  6:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-19 18:05 [BUG 1/3] smb: client: SMB2/3 signature failures are logged but the response is accepted Birtwhistle, Daniel
2026-07-20  6:10 ` Willy Tarreau
2026-07-20  6:13 ` Greg KH [this message]
2026-07-20 11:51   ` Birtwhistle, Daniel

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=2026072010-affront-blog-f082@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.birtwhistle@gehealthcare.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@manguebit.org \
    --cc=security@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