Strix
26.1K

CVE-2025-40118

HIGHCVSS 7.8/10EPSS 0.21%

Last modified

CVE-2025-40118 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.21%

11.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 05b512879eab41faa515b67fa3896d0005e97909, < d94be0a6ae9ade706d4270e740bdb4f79953a7fc; >= bc2140c8136200b4437e1abc0fb659968cb9baab, < 45acbf154befedd9bc135f5e031fe7855d1e6493; >= 1d8f9378cb4800c18e20d80ecd605b2b93e87a03, < eef5ef400893f8e3dbb09342583be0cdc716d566; >= 30e482dfb8f27d22f518695d4bcb5e7f4c6cb08a, < 9c671d4dbfbfb0d73cfdfb706afb36d9ad60a582; >= a862d24e1fc3ab1b5e5f20878d2898cea346d0ec, < e62251954a128a2d0fcbc19e5fa39e08935bb628; >= 0f9802f174227f553959422f844eeb9ba72467fe, < 9326a1541e1b7ed3efdbab72061b82cf01c6477a; >= f7b705c238d1483f0a766e2b20010f176e5c0fb7, < 83ced3c206c292458e47c7fac54223abc7141585; >= f7b705c238d1483f0a766e2b20010f176e5c0fb7, < 251be2f6037fb7ab399f68cd7428ff274133d693; 722026c010fa75bcf9e2373aff1d7930a3d7e3cf; >= 5.4.293, < 5.4.301; >= 5.10.237, < 5.10.246; >= 5.15.181, < 5.15.195; >= 6.1.136, < 6.1.156; >= 6.6.89, < 6.6.112; >= 6.12.26, < 6.12.53; >= 6.14.5, < 6.15
LinuxLinux6.15

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-40118?
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.
How severe is CVE-2025-40118?
CVE-2025-40118 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2025-40118?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

View all 2025CVEs →

Are you affected by CVE-2025-40118?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST