[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025040136-CVE-2025-21947-fcc5@gregkh>
Date: Tue, 1 Apr 2025 16:40:11 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-21947: ksmbd: fix type confusion via race condition when using ipc_msg_send_request
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix type confusion via race condition when using ipc_msg_send_request
req->handle is allocated using ksmbd_acquire_id(&ipc_ida), based on
ida_alloc. req->handle from ksmbd_ipc_login_request and
FSCTL_PIPE_TRANSCEIVE ioctl can be same and it could lead to type confusion
between messages, resulting in access to unexpected parts of memory after
an incorrect delivery. ksmbd check type of ipc response but missing add
continue to check next ipc reponse.
The Linux kernel CVE team has assigned CVE-2025-21947 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.131 with commit 6321bbda4244b93802d61cfe0887883aae322f4b
Fixed in 6.6.83 with commit 76861630b29e51373e73e7b00ad0d467b6941162
Fixed in 6.12.19 with commit 3cb2b2e41541fe6f9cc55ca22d4c0bd260498aea
Fixed in 6.13.7 with commit 1e8833c03a38e1d5d5df6484e3f670a2fd38fb76
Fixed in 6.14 with commit e2ff19f0b7a30e03516e6eb73b948e27a55bc9d2
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-2025-21947
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/smb/server/transport_ipc.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/6321bbda4244b93802d61cfe0887883aae322f4b
https://git.kernel.org/stable/c/76861630b29e51373e73e7b00ad0d467b6941162
https://git.kernel.org/stable/c/3cb2b2e41541fe6f9cc55ca22d4c0bd260498aea
https://git.kernel.org/stable/c/1e8833c03a38e1d5d5df6484e3f670a2fd38fb76
https://git.kernel.org/stable/c/e2ff19f0b7a30e03516e6eb73b948e27a55bc9d2
Powered by blists - more mailing lists