From: Paulo Alcantara <pc@manguebit.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] smb client fixes for 7.4-rc4
Date: Sat, 21 Nov 2026 13:53:39 -0300 [thread overview]
Message-ID: <bada6649ca5eb9e4603216c71aff0a85@manguebit.org> (raw)
Linus,
Please consider pulling these smb client fixes for v7.4-rc4. The main
ones are a server-triggerable use-after-free and two fixes that stop the
client from accepting SMB2 responses and read data with a bad signature;
the rest are a couple of busy-inode-on-unmount races and some metadata
fixes. All of them are for stable.
Thanks,
Paulo
----------------------------------------------------------------
The following changes since commit 3db1c74a20f0552fadc2c6886a43feee8894fa19:
Merge tag 'cifs-fixes-7.4-rc3' of https://git.manguebit.org/linux (2026-11-13 09:56:22 -0800)
are available in the Git repository at:
https://git.manguebit.org/linux.git tags/cifs-fixes-7.4-rc4
for you to fetch changes up to a1a0ef3ba8e802060bfc2b0ebf131a2cf98c3b71:
smb: client: don't use read data that failed signature verification (2026-11-19 12:02:54 -0300)
----------------------------------------------------------------
smb client fixes for v7.4-rc4
- Fix a use-after-free in the netfs write collector that a malicious or
broken server can trigger by returning a write count larger than the
request
- Reject SMB2 responses whose signature fails verification instead of
using them, so a tampered response on a signed connection is no
longer accepted
- Don't return read data whose signature failed verification when the
read lands at the remote end of file
- Fix a busy inode and dentry on unmount caused by a late oplock break
queued after the workqueues were already flushed
- Fix a busy dentry on unmount caused by a persistent-handle reopen
racing the unmount
- Fix creation and change time assignments in the SMB2 POSIX readdir
path, which clobbered ctime and could give a hard link a separate
in-memory inode
- Normalise pre-epoch timestamps read from the server so stat no longer
reports a garbled time
- Fix DFS prefix paths being truncated on non-utf8 mounts, where
path_consumed was applied in the wrong charset and the mount failed
with -ENOENT
----------------------------------------------------------------
Fredric Cover (1):
smb: client: convert path_consumed to mount charset units
Siddharth Chintamaneni (2):
smb: client: fix busy dentry and inode on unmount from late oplock break
smb: client: fix busy dentry on unmount from persistent handle reopen
Suyuan Wang (2):
smb: client: fail SMB2 responses with a bad signature
smb: client: don't use read data that failed signature verification
koraynilay (2):
smb: client: fix negative timestamps being read from smb
smb: client: fix times assignments in cifs_posix_to_fattr()
ozgun kultekin (1):
smb: client: do not let the server grow a write subrequest
fs/smb/client/cifsfs.c | 10 +++---
fs/smb/client/dfs.c | 77 +++++++++++++++++++++++++++++++++++++++++--
fs/smb/client/file.c | 8 +++++
fs/smb/client/misc.c | 6 +++-
fs/smb/client/netmisc.c | 3 +-
fs/smb/client/readdir.c | 3 +-
fs/smb/client/smb2pdu.c | 22 +++++++++----
fs/smb/client/smb2transport.c | 7 ++--
fs/smb/client/trace.h | 1 +
fs/smb/client/transport.c | 5 +++
10 files changed, 122 insertions(+), 20 deletions(-)
reply other threads:[~2026-11-21 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bada6649ca5eb9e4603216c71aff0a85@manguebit.org \
--to=pc@manguebit.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®