linux-cve-announce - CVE-2024-42288: scsi: qla2xxx: Fix for possible memory corruption

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: <2024081745-CVE-2024-42288-c59b@gregkh>
Date: Sat, 17 Aug 2024 11:09:53 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-42288: scsi: qla2xxx: Fix for possible memory corruption

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

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

scsi: qla2xxx: Fix for possible memory corruption

Init Control Block is dereferenced incorrectly.  Correctly dereference ICB

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


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

	Fixed in 6.1.103 with commit 2a15b59a2c5a
	Fixed in 6.6.44 with commit 571d7f2a0883
	Fixed in 6.10.3 with commit 8192c533e89d
	Fixed in 6.11-rc1 with commit c03d740152f7

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-42288
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/qla2xxx/qla_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/2a15b59a2c5afac89696e44acf5bbfc0599c6c5e
	https://git.kernel.org/stable/c/571d7f2a08836698c2fb0d792236424575b9829b
	https://git.kernel.org/stable/c/8192c533e89d9fb69b2490398939236b78cda79b
	https://git.kernel.org/stable/c/c03d740152f78e86945a75b2ad541bf972fab92a