Linux Kernel up to 6.17.2 scsi pm8001_sas.c phy_attached array index

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.17.2. Affected by this issue is the function phy_attached of the file drivers/scsi/pm8001/pm8001_sas.c of the component scsi. This manipulation causes array index.
The identification of this vulnerability is CVE-2025-40118. There is no exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 6.17.2. It has been declared as critical. Affected by this vulnerability is the function phy_attached of the file drivers/scsi/pm8001/pm8001_sas.c of the component scsi. The manipulation with an unknown input leads to a array index vulnerability. The CWE definition for the vulnerability is CWE-129. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2025-40118 since 04/16/2025. The exploitation appears to be easy. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/07/2026).
The vulnerability scanner Nessus provides a plugin with the ID 275236 (Linux Distros Unpatched Vulnerability : CVE-2025-40118), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.4.301, 5.10.246, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.17.3 or 6.18-rc1 eliminates this vulnerability. Applying the patch d94be0a6ae9ade706d4270e740bdb4f79953a7fc/45acbf154befedd9bc135f5e031fe7855d1e6493/eef5ef400893f8e3dbb09342583be0cdc716d566/9c671d4dbfbfb0d73cfdfb706afb36d9ad60a582/e62251954a128a2d0fcbc19e5fa39e08935bb628/9326a1541e1b7ed3efdbab72061b82cf01c6477a/83ced3c206c292458e47c7fac54223abc7141585/251be2f6037fb7ab399f68cd7428ff274133d693 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (275236) and CERT Bund (WID-SEC-2025-2579). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Google Container-Optimized OS
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- Open Source Linux Kernel
- RESF Rocky Linux
Product
Type
Vendor
Name
Version
- 5.0
- 5.1
- 5.2
- 5.3
- 5.4.300
- 5.10.245
- 5.15.194
- 6.1.155
- 6.6.111
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
- 6.12.8
- 6.12.9
- 6.12.10
- 6.12.11
- 6.12.12
- 6.12.13
- 6.12.14
- 6.12.15
- 6.12.16
- 6.12.17
- 6.12.18
- 6.12.19
- 6.12.20
- 6.12.21
- 6.12.22
- 6.12.23
- 6.12.24
- 6.12.25
- 6.12.26
- 6.12.27
- 6.12.28
- 6.12.29
- 6.12.30
- 6.12.31
- 6.12.32
- 6.12.33
- 6.12.34
- 6.12.35
- 6.12.36
- 6.12.37
- 6.12.38
- 6.12.39
- 6.12.40
- 6.12.41
- 6.12.42
- 6.12.43
- 6.12.44
- 6.12.45
- 6.12.46
- 6.12.47
- 6.12.48
- 6.12.49
- 6.12.50
- 6.12.51
- 6.12.52
- 6.17.0
- 6.17.1
- 6.17.2
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.6
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Array indexCWE: CWE-129 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 275236
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-40118
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.4.301/5.10.246/5.15.195/6.1.156/6.6.112/6.12.53/6.17.3/6.18-rc1
Patch: d94be0a6ae9ade706d4270e740bdb4f79953a7fc/45acbf154befedd9bc135f5e031fe7855d1e6493/eef5ef400893f8e3dbb09342583be0cdc716d566/9c671d4dbfbfb0d73cfdfb706afb36d9ad60a582/e62251954a128a2d0fcbc19e5fa39e08935bb628/9326a1541e1b7ed3efdbab72061b82cf01c6477a/83ced3c206c292458e47c7fac54223abc7141585/251be2f6037fb7ab399f68cd7428ff274133d693
Timeline
04/16/2025 CVE reserved11/12/2025 Advisory disclosed
11/12/2025 VulDB entry created
02/07/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2025-40118 (🔒)
GCVE (CVE): GCVE-0-2025-40118
GCVE (VulDB): GCVE-100-332179
CERT Bund: WID-SEC-2025-2579 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 11/12/2025 13:38Updated: 02/07/2026 21:49
Changes: 11/12/2025 13:38 (60), 11/13/2025 09:51 (7), 11/13/2025 11:27 (2), 12/18/2025 01:16 (1), 12/30/2025 13:38 (1), 02/07/2026 21:49 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.