[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025081612-CVE-2023-32246-2e6d@gregkh>
Date: Sat, 16 Aug 2025 15:22:13 +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-32246: ksmbd: call rcu_barrier() in ksmbd_server_exit()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: call rcu_barrier() in ksmbd_server_exit()
racy issue is triggered the bug by racing between closing a connection
and rmmod. In ksmbd, rcu_barrier() is not called at module unload time,
so nothing prevents ksmbd from getting unloaded while it still has RCU
callbacks pending. It leads to trigger unintended execution of kernel
code locally and use to defeat protections such as Kernel Lockdown
The Linux kernel CVE team has assigned CVE-2023-32246 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.111 with commit c053e389db0d892e2ff5a60ec5e533b976503795
Fixed in 6.1.28 with commit b80422474ffe44cb5e813cd6da1f1c6bc50fd9d2
Fixed in 6.2.15 with commit d4174505016a3b2996eb7ff1530dcabbf15d47b6
Fixed in 6.3.2 with commit 5a7090ccc242ab009ee7769e9d7fad6644dbe9bd
Fixed in 6.4 with commit eb307d09fe15844fdaebeb8cc8c9b9e925430aa5
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-32246
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/server.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/c053e389db0d892e2ff5a60ec5e533b976503795
https://git.kernel.org/stable/c/b80422474ffe44cb5e813cd6da1f1c6bc50fd9d2
https://git.kernel.org/stable/c/d4174505016a3b2996eb7ff1530dcabbf15d47b6
https://git.kernel.org/stable/c/5a7090ccc242ab009ee7769e9d7fad6644dbe9bd
https://git.kernel.org/stable/c/eb307d09fe15844fdaebeb8cc8c9b9e925430aa5
Powered by blists - more mailing lists