linux-cve-announce - CVE-2024-57925: ksmbd: fix a missing return value check bug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025011944-CVE-2024-57925-b738@gregkh>
Date: Sun, 19 Jan 2025 12:52:56 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-57925: ksmbd: fix a missing return value check bug

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix a missing return value check bug

In the smb2_send_interim_resp(), if ksmbd_alloc_work_struct()
fails to allocate a node, it returns a NULL pointer to the
in_work pointer. This can lead to an illegal memory write of
in_work->response_buf when allocate_interim_rsp_buf() attempts
to perform a kzalloc() on it.

To address this issue, incorporating a check for the return
value of ksmbd_alloc_work_struct() ensures that the function
returns immediately upon allocation failure, thereby preventing
the aforementioned illegal memory access.

The Linux kernel CVE team has assigned CVE-2024-57925 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.1.71 with commit f8cf1ebb7de62c7d807707ce4abb69d483629263 and fixed in 6.1.125 with commit ee7e40f7fb17f08a8cbae50553e5c2e10ae32fce
	Issue introduced in 6.6 with commit 041bba4414cda37d00063952c9bff9c3d5812a19 and fixed in 6.6.72 with commit 271ae0edbfc942795c162e6cf20d2bc02bd7fde4
	Issue introduced in 6.6 with commit 041bba4414cda37d00063952c9bff9c3d5812a19 and fixed in 6.12.10 with commit 2976e91a3e569cf2c92c9f71512c0ab1312fe965
	Issue introduced in 6.6 with commit 041bba4414cda37d00063952c9bff9c3d5812a19 and fixed in 6.13-rc7 with commit 4c16e1cadcbcaf3c82d5fc310fbd34d0f5d0db7c
	Issue introduced in 5.15.145 with commit 6f0207218c4c125f5bf32055ac4220b4ef3b7e67

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-2024-57925
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/ee7e40f7fb17f08a8cbae50553e5c2e10ae32fce
	https://git.kernel.org/stable/c/271ae0edbfc942795c162e6cf20d2bc02bd7fde4
	https://git.kernel.org/stable/c/2976e91a3e569cf2c92c9f71512c0ab1312fe965
	https://git.kernel.org/stable/c/4c16e1cadcbcaf3c82d5fc310fbd34d0f5d0db7c