From: Michail Andreas Michalopoulos <mike.michalo@gmail.com>
To: linkinjeon@kernel.org, stfrench@microsoft.com
Cc: icb@fastmail.org, senozhatsky@chromium.org, tom@talpey.com,
chenxiaosong@chenxiaosong.com, ematsumiya@suse.de,
lsahlber@redhat.com, hyc.lee@gmail.com,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
Michail Andreas Michalopoulos <mike.michalo@gmail.com>
Subject: [PATCH v2 0/4] ksmbd: verify session setup requests before signing with their key
Date: Fri, 6 Nov 2026 20:06:18 +0100 [thread overview]
Message-ID: <20261106190622.20990-1-mike.michalo@gmail.com> (raw)
In-Reply-To: <20261103171742.18816-1-icb@fastmail.org>
ksmbd signs some SESSION_SETUP and error responses with a session's key
without having verified the request, which lets a peer that does not hold
the key obtain signatures made with it. This series fixes those cases and
makes ksmbd sign with the SMB 3.1.1 signing algorithm it negotiated.
1/4 verifies multichannel binding requests with the session signing key
(MS-SMB2 3.3.5.2.4), as reported by Ian Bridges.
2/4 keeps the negotiated SMB 3.1.1 signing algorithm instead of always
using AES-CMAC, and signs each key with its own algorithm.
3/4 verifies signed reauthentication requests and uses the channel key
for session setup on a bound channel. A reauthentication with a
forged signature used to get a response signed with the session key.
4/4 checks the MessageId and signature of a request before signing
STATUS_NETWORK_SESSION_EXPIRED, also reported by Ian Bridges.
Changes since v1:
- 1/4 is new: verify the signature of session binding requests, as
reported by Ian Bridges.
- 2/4 (v1 1/2): reset the negotiated signing state on every NEGOTIATE;
Cc stable, since 3/4 depends on it.
- 3/4 and 4/4 are new.
- The AES-GMAC signing patch (v1 2/2) is dropped from this series and
will be posted separately.
Testing, on a KASAN/lockdep UML kernel with ksmbd-tools: forged and
replayed binding, reauthentication and expired-session requests, also
inside compounds, get unsigned refusals with AES-CMAC and HMAC-SHA256;
randomized requests against these paths and concurrent bind/reauth/
logoff stress found no signed response to an unverified request and no
KASAN or lockdep report; the Linux cifs client works with SMB 2.1 to
3.1.1, signed and encrypted; smbtorture's session, signing, I/O,
compound, lock, oplock, lease, notify and ioctl suites give the same
results as without the series. Ian Bridges also tested an earlier
revision with his own probes and smbtorture. Not tested: Windows
clients, and Kerberos expiry with a real KDC (it was emulated with a
test-only change).
An AI assistant was used to draft the patches and as an independent
reviewer.
Michail Andreas Michalopoulos (4):
ksmbd: verify the signature of session binding requests
ksmbd: sign with the negotiated SMB 3.1.1 signing algorithm
ksmbd: use the channel signing key for session setup on a bound
channel
ksmbd: check a request before signing STATUS_NETWORK_SESSION_EXPIRED
fs/smb/server/auth.c | 14 +++-
fs/smb/server/auth.h | 4 +-
fs/smb/server/mgmt/user_session.c | 1 +
fs/smb/server/mgmt/user_session.h | 2 +
fs/smb/server/server.c | 39 +++++++++-
fs/smb/server/smb2ops.c | 4 +-
fs/smb/server/smb2pdu.c | 114 +++++++++++++++++++++++++-----
7 files changed, 154 insertions(+), 24 deletions(-)
base-commit: 05441d697f7f9a927264f4058cbbc6a03dfcac9d
--
2.43.0
next prev parent reply other threads:[~2026-11-06 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 11:14 [PATCH 0/2] ksmbd: AES-GMAC signing support Michail Andreas Michalopoulos
2026-11-03 11:14 ` [PATCH 1/2] ksmbd: sign with the negotiated SMB 3.1.1 signing algorithm Michail Andreas Michalopoulos
2026-11-03 11:14 ` [PATCH 2/2] ksmbd: add AES-GMAC signing support Michail Andreas Michalopoulos
2026-11-03 17:17 ` Ian Bridges
2026-11-03 17:57 ` mixalhs
2026-11-04 4:30 ` Namjae Jeon
2026-11-06 19:06 ` Michail Andreas Michalopoulos [this message]
2026-11-06 19:06 ` [PATCH v2 1/4] ksmbd: verify the signature of session binding requests Michail Andreas Michalopoulos
2026-11-06 19:06 ` [PATCH v2 2/4] ksmbd: sign with the negotiated SMB 3.1.1 signing algorithm Michail Andreas Michalopoulos
2026-11-06 19:06 ` [PATCH v2 3/4] ksmbd: use the channel signing key for session setup on a bound channel Michail Andreas Michalopoulos
2026-11-06 19:06 ` [PATCH v2 4/4] ksmbd: check a request before signing STATUS_NETWORK_SESSION_EXPIRED Michail Andreas Michalopoulos
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=20261106190622.20990-1-mike.michalo@gmail.com \
--to=mike.michalo@gmail.com \
--cc=chenxiaosong@chenxiaosong.com \
--cc=ematsumiya@suse.de \
--cc=hyc.lee@gmail.com \
--cc=icb@fastmail.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=senozhatsky@chromium.org \
--cc=stfrench@microsoft.com \
--cc=tom@talpey.com \
/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
all inboxes | Powered by JetHome®