[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025052002-CVE-2025-37956-a6aa@gregkh>
Date: Tue, 20 May 2025 18:02:10 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-37956: ksmbd: prevent rename with empty string
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: prevent rename with empty string
Client can send empty newname string to ksmbd server.
It will cause a kernel oops from d_alloc.
This patch return the error when attempting to rename
a file or directory with an empty new name string.
The Linux kernel CVE team has assigned CVE-2025-37956 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.91 with commit 6ee551672c8cf36108b0cfba92ec0c7c28ac3439
Fixed in 6.12.29 with commit c57301e332cc413fe0a7294a90725f4e21e9549d
Fixed in 6.14.7 with commit d7f2c00acb1ef64304fd40ac507e9213ff1d9b5c
Fixed in 6.15-rc6 with commit 53e3e5babc0963a92d856a5ec0ce92c59f54bc12
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-37956
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/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/6ee551672c8cf36108b0cfba92ec0c7c28ac3439
https://git.kernel.org/stable/c/c57301e332cc413fe0a7294a90725f4e21e9549d
https://git.kernel.org/stable/c/d7f2c00acb1ef64304fd40ac507e9213ff1d9b5c
https://git.kernel.org/stable/c/53e3e5babc0963a92d856a5ec0ce92c59f54bc12
Powered by blists - more mailing lists