scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0f9802f174227f553959422f844eeb9ba72467fe · < 9326a1541e1b7ed3efdbab72061b82cf01c6477a| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's pm80xx SCSI driver can index beyond its local PHY array when a device is connected through an expander. UBSAN reports the out-of-bounds access during module removal (rmmod); the input does not describe an attacker scenario, authentication requirement, or user interaction.
Engineers running Linux kernels with the pm80xx SCSI driver and devices connected through an expander should check their systems; affected versions are not specified.