linux-cve-announce - CVE-2023-54234: scsi: mpi3mr: Fix missing mrioc->evtack

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: <2025123031-CVE-2023-54234-bb5c@gregkh>
Date: Tue, 30 Dec 2025 13:14:04 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54234: scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization

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

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

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

scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization

Commit c1af985d27da ("scsi: mpi3mr: Add Event acknowledgment logic")
introduced an array mrioc->evtack_cmds but initialization of the array
elements was missed. They are just zero cleared. The function
mpi3mr_complete_evt_ack() refers host_tag field of the elements. Due to the
zero value of the host_tag field, the function calls clear_bit() for
mrico->evtack_cmds_bitmap with wrong bit index. This results in memory
access to invalid address and "BUG: KASAN: use-after-free". This BUG was
observed at eHBA-9600 firmware update to version 8.3.1.0. To fix it, add
the missing initialization of mrioc->evtack_cmds.

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


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

	Issue introduced in 5.17 with commit c1af985d27da2d530c22604644e9025810f57d7c and fixed in 6.1.16 with commit 4e0dfdb48a824deac3dfbc67fb856ef2aee13529
	Issue introduced in 5.17 with commit c1af985d27da2d530c22604644e9025810f57d7c and fixed in 6.2.3 with commit 67989091e11a974003ddf2ec39bc613df8eadd83
	Issue introduced in 5.17 with commit c1af985d27da2d530c22604644e9025810f57d7c and fixed in 6.3 with commit e39ea831ebad4ab15c4748cb62a397a8abcca36e

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-54234
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_os.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/4e0dfdb48a824deac3dfbc67fb856ef2aee13529
	https://git.kernel.org/stable/c/67989091e11a974003ddf2ec39bc613df8eadd83
	https://git.kernel.org/stable/c/e39ea831ebad4ab15c4748cb62a397a8abcca36e