Message-ID: <2025111252-CVE-2025-40118-19e2@gregkh>
Date: Wed, 12 Nov 2025 19:23:54 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40118: scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod

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

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

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

scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod

Since commit f7b705c238d1 ("scsi: pm80xx: Set phy_attached to zero when
device is gone") UBSAN reports:

  UBSAN: array-index-out-of-bounds in drivers/scsi/pm8001/pm8001_sas.c:786:17
  index 28 is out of range for type 'pm8001_phy [16]'

on rmmod when using an expander.

For a direct attached device, attached_phy contains the local phy id.
For a device behind an expander, attached_phy contains the remote phy
id, not the local phy id.

I.e. while pm8001_ha will have pm8001_ha->chip->n_phy local phys, for a
device behind an expander, attached_phy can be much larger than
pm8001_ha->chip->n_phy (depending on the amount of phys of the
expander).

E.g. on my system pm8001_ha has 8 phys with phy ids 0-7.  One of the
ports has an expander connected.  The expander has 31 phys with phy ids
0-30.

The pm8001_ha->phy array only contains the phys of the HBA.  It does not
contain the phys of the expander.  Thus, it is wrong to use attached_phy
to index the pm8001_ha->phy array for a device behind an expander.

Thus, we can only clear phy_attached for devices that are directly
attached.

The Linux kernel CVE team has assigned CVE-2025-40118 to this issue.


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

	Issue introduced in 5.4.293 with commit 05b512879eab41faa515b67fa3896d0005e97909 and fixed in 5.4.301 with commit d94be0a6ae9ade706d4270e740bdb4f79953a7fc
	Issue introduced in 5.10.237 with commit bc2140c8136200b4437e1abc0fb659968cb9baab and fixed in 5.10.246 with commit 45acbf154befedd9bc135f5e031fe7855d1e6493
	Issue introduced in 5.15.181 with commit 1d8f9378cb4800c18e20d80ecd605b2b93e87a03 and fixed in 5.15.195 with commit eef5ef400893f8e3dbb09342583be0cdc716d566
	Issue introduced in 6.1.136 with commit 30e482dfb8f27d22f518695d4bcb5e7f4c6cb08a and fixed in 6.1.156 with commit 9c671d4dbfbfb0d73cfdfb706afb36d9ad60a582
	Issue introduced in 6.6.89 with commit a862d24e1fc3ab1b5e5f20878d2898cea346d0ec and fixed in 6.6.112 with commit e62251954a128a2d0fcbc19e5fa39e08935bb628
	Issue introduced in 6.12.26 with commit 0f9802f174227f553959422f844eeb9ba72467fe and fixed in 6.12.53 with commit 9326a1541e1b7ed3efdbab72061b82cf01c6477a
	Issue introduced in 6.15 with commit f7b705c238d1483f0a766e2b20010f176e5c0fb7 and fixed in 6.17.3 with commit 83ced3c206c292458e47c7fac54223abc7141585
	Issue introduced in 6.15 with commit f7b705c238d1483f0a766e2b20010f176e5c0fb7 and fixed in 6.18-rc1 with commit 251be2f6037fb7ab399f68cd7428ff274133d693
	Issue introduced in 6.14.5 with commit 722026c010fa75bcf9e2373aff1d7930a3d7e3cf

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-40118
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/pm8001/pm8001_sas.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/d94be0a6ae9ade706d4270e740bdb4f79953a7fc
	https://git.kernel.org/stable/c/45acbf154befedd9bc135f5e031fe7855d1e6493
	https://git.kernel.org/stable/c/eef5ef400893f8e3dbb09342583be0cdc716d566
	https://git.kernel.org/stable/c/9c671d4dbfbfb0d73cfdfb706afb36d9ad60a582
	https://git.kernel.org/stable/c/e62251954a128a2d0fcbc19e5fa39e08935bb628
	https://git.kernel.org/stable/c/9326a1541e1b7ed3efdbab72061b82cf01c6477a
	https://git.kernel.org/stable/c/83ced3c206c292458e47c7fac54223abc7141585
	https://git.kernel.org/stable/c/251be2f6037fb7ab399f68cd7428ff274133d693

Powered by blists - more mailing lists