SECUFOCUSNOW
Home›CVE index›CVE-2025-40118
Review reviewHigh

CVE-2025-40118

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->...

CVSS
7.8
EPSS
0.15%
4.79% percentile
CISA KEV
Not listed
Published
2025.11.12
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.15%
Technical severityCVSS 7.8

Vulnerability overview

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->...

Affected product and versions

Product
Linux
Affected versions
>= 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, >= 6.15
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available
CVE-2025-40118 — Linux | SECUFOCUS NOW