linux-cve-announce - CVE-2023-53320: scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2025091644-CVE-2023-53320-d419@gregkh>
Date: Tue, 16 Sep 2025 18:12: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-2023-53320: scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info()

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

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

scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info()

The function mpi3mr_get_all_tgt_info() has four issues:

1) It calculates valid entry length in alltgt_info assuming the header part
   of the struct mpi3mr_device_map_info would equal to sizeof(u32).  The
   correct size is sizeof(u64).

2) When it calculates the valid entry length kern_entrylen, it excludes one
   entry by subtracting 1 from num_devices.

3) It copies num_device by calling memcpy(). Substitution is enough.

4) It does not specify the calculated length to sg_copy_from_buffer().
   Instead, it specifies the payload length which is larger than the
   alltgt_info size. It causes "BUG: KASAN: slab-out-of-bounds".

Fix the issues by using the correct header size, removing the subtraction
from num_devices, replacing the memcpy() with substitution and specifying
the correct length to sg_copy_from_buffer().

The Linux kernel CVE team has assigned CVE-2023-53320 to this issue.

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

	Issue introduced in 5.19 with commit f5e6d5a343761081317c89d23489c93fbafc69ff and fixed in 6.1.16 with commit 8ba997b22f2cd5d29aad8c39f6201f7608ed0c04
	Issue introduced in 5.19 with commit f5e6d5a343761081317c89d23489c93fbafc69ff and fixed in 6.2.3 with commit 2f3d3fa5b8ed7d3b147478f42b00b468eeb1ecd2
	Issue introduced in 5.19 with commit f5e6d5a343761081317c89d23489c93fbafc69ff and fixed in 6.3 with commit fb428a2005fc1260d18b989cc5199f281617f44d

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-53320
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/mpi3mr/mpi3mr_app.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/8ba997b22f2cd5d29aad8c39f6201f7608ed0c04
	https://git.kernel.org/stable/c/2f3d3fa5b8ed7d3b147478f42b00b468eeb1ecd2
	https://git.kernel.org/stable/c/fb428a2005fc1260d18b989cc5199f281617f44d