[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025090452-CVE-2025-38700-0c1b@gregkh>
Date: Thu, 4 Sep 2025 17:33:05 +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-38700: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated
In case of an ib_fast_reg_mr allocation failure during iSER setup, the
machine hits a panic because iscsi_conn->dd_data is initialized
unconditionally, even when no memory is allocated (dd_size == 0). This
leads invalid pointer dereference during connection teardown.
Fix by setting iscsi_conn->dd_data only if memory is actually allocated.
Panic trace:
------------
iser: iser_create_fastreg_desc: Failed to allocate ib_fast_reg_mr err=-12
iser: iser_alloc_rx_descriptors: failed allocating rx descriptors / data buffers
BUG: unable to handle page fault for address: fffffffffffffff8
RIP: 0010:swake_up_locked.part.5+0xa/0x40
Call Trace:
complete+0x31/0x40
iscsi_iser_conn_stop+0x88/0xb0 [ib_iser]
iscsi_stop_conn+0x66/0xc0 [scsi_transport_iscsi]
iscsi_if_stop_conn+0x14a/0x150 [scsi_transport_iscsi]
iscsi_if_rx+0x1135/0x1834 [scsi_transport_iscsi]
? netlink_lookup+0x12f/0x1b0
? netlink_deliver_tap+0x2c/0x200
netlink_unicast+0x1ab/0x280
netlink_sendmsg+0x257/0x4f0
? _copy_from_user+0x29/0x60
sock_sendmsg+0x5f/0x70
The Linux kernel CVE team has assigned CVE-2025-38700 to this issue.
Affected and fixed versions
===========================
Fixed in 5.4.297 with commit f53af99f441ee79599d8df6113a7144d74cf9153
Fixed in 5.10.241 with commit 9ea6d961566c7d762ed0204b06db05756fdda3b6
Fixed in 5.15.190 with commit fd5aad080edb501ab5c84b7623d612d0e3033403
Fixed in 6.1.149 with commit a145c269dc5380c063a20a0db7e6df2995962e9d
Fixed in 6.6.103 with commit 66a373f50b4249d57f5a88c7be9676f9d5884865
Fixed in 6.12.43 with commit 35782c32528d82aa21f84cb5ceb2abd3526a8159
Fixed in 6.15.11 with commit a33d42b7fc24fe03f239fbb0880dd5b4b4b97c19
Fixed in 6.16.2 with commit 2b242ea14386a510010eabfbfc3ce81a101f3802
Fixed in 6.17-rc1 with commit 3ea3a256ed81f95ab0f3281a0e234b01a9cae605
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-38700
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:
drivers/scsi/libiscsi.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/f53af99f441ee79599d8df6113a7144d74cf9153
https://git.kernel.org/stable/c/9ea6d961566c7d762ed0204b06db05756fdda3b6
https://git.kernel.org/stable/c/fd5aad080edb501ab5c84b7623d612d0e3033403
https://git.kernel.org/stable/c/a145c269dc5380c063a20a0db7e6df2995962e9d
https://git.kernel.org/stable/c/66a373f50b4249d57f5a88c7be9676f9d5884865
https://git.kernel.org/stable/c/35782c32528d82aa21f84cb5ceb2abd3526a8159
https://git.kernel.org/stable/c/a33d42b7fc24fe03f239fbb0880dd5b4b4b97c19
https://git.kernel.org/stable/c/2b242ea14386a510010eabfbfc3ce81a101f3802
https://git.kernel.org/stable/c/3ea3a256ed81f95ab0f3281a0e234b01a9cae605
Powered by blists - more mailing lists