[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091721-CVE-2023-53358-29d3@gregkh>
Date: Wed, 17 Sep 2025 16:56:57 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53358: ksmbd: fix racy issue under cocurrent smb2 tree disconnect
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix racy issue under cocurrent smb2 tree disconnect
There is UAF issue under cocurrent smb2 tree disconnect.
This patch introduce TREE_CONN_EXPIRE flags for tcon to avoid cocurrent
access.
The Linux kernel CVE team has assigned CVE-2023-53358 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.145 with commit b36295c17fb97424406f0c3ab321b1ccaabb9be8
Fixed in 6.1.28 with commit bd80d35725a0cf4df9307bfe2f1a3b2cb983d8e6
Fixed in 6.2.15 with commit dc1c17716c099c90948ebb83e2170dd75a3be6b6
Fixed in 6.3.2 with commit 39366b47a59d46af15ac57beb0996268bf911f6a
Fixed in 6.4 with commit 30210947a343b6b3ca13adc9bfc88e1543e16dd5
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-53358
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/ksmbd/mgmt/tree_connect.c
fs/ksmbd/mgmt/tree_connect.h
fs/ksmbd/smb2pdu.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/b36295c17fb97424406f0c3ab321b1ccaabb9be8
https://git.kernel.org/stable/c/bd80d35725a0cf4df9307bfe2f1a3b2cb983d8e6
https://git.kernel.org/stable/c/dc1c17716c099c90948ebb83e2170dd75a3be6b6
https://git.kernel.org/stable/c/39366b47a59d46af15ac57beb0996268bf911f6a
https://git.kernel.org/stable/c/30210947a343b6b3ca13adc9bfc88e1543e16dd5
Powered by blists - more mailing lists