linux-cve-announce - CVE-2023-53376: scsi: mpi3mr: Use number of bits to manage bitmap sizes

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: <2025091856-CVE-2023-53376-d18b@gregkh>
Date: Thu, 18 Sep 2025 15:34:21 +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-53376: scsi: mpi3mr: Use number of bits to manage bitmap sizes

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

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

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

scsi: mpi3mr: Use number of bits to manage bitmap sizes

To allocate bitmaps, the mpi3mr driver calculates sizes of bitmaps using
byte as unit. However, bitmap helper functions assume that bitmaps are
allocated using unsigned long as unit. This gap causes memory access beyond
the bitmap sizes and results in "BUG: KASAN: slab-out-of-bounds".  The BUG
was observed at firmware download to eHBA-9600. Call trace indicated that
the out-of-bounds access happened in find_first_zero_bit() called from
mpi3mr_send_event_ack() for miroc->evtack_cmds_bitmap.

To fix the BUG, do not use bytes to manage bitmap sizes. Instead, use
number of bits, and call bitmap helper functions which take number of bits
as arguments. For memory allocation, call bitmap_zalloc() instead of
kzalloc() and krealloc(). For memory free, call bitmap_free() instead of
kfree(). For zero clear, call bitmap_clear() instead of memset().

Remove three fields for bitmap byte sizes in struct scmd_priv which are no
longer required. Replace the field dev_handle_bitmap_sz with
dev_handle_bitmap_bits to keep number of bits of removepend_bitmap across
resize.

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

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

	Issue introduced in 5.14 with commit 824a156633dfdb0e17979a0d0bb2c757d1bb949c and fixed in 6.1.18 with commit 6a675a6d57d31da43d8da576465c1cd5d5b0bd3d
	Issue introduced in 5.14 with commit 824a156633dfdb0e17979a0d0bb2c757d1bb949c and fixed in 6.2.5 with commit 8ac713d2e9845e9234bb12ae5903040685d5aff9
	Issue introduced in 5.14 with commit 824a156633dfdb0e17979a0d0bb2c757d1bb949c and fixed in 6.3 with commit 339e61565f81a6534afdc18fd854b2e2628bf5db

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-53376
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.h
	drivers/scsi/mpi3mr/mpi3mr_fw.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/6a675a6d57d31da43d8da576465c1cd5d5b0bd3d
	https://git.kernel.org/stable/c/8ac713d2e9845e9234bb12ae5903040685d5aff9
	https://git.kernel.org/stable/c/339e61565f81a6534afdc18fd854b2e2628bf5db